quality/tickets
9
1
Fork 0
Code Issues 57 Projects Activity Actions

GRUB Out-Of-Memory Error Test Day - Second Part #862

New issue
Open
opened 2026-01-20 18:07:05 +00:00 by lsandova · 17 comments
lsandova commented 2026-01-20 18:07:05 +00:00
Copy link

Test day proposal

We have a new fix [1] and hopefully this time would be the final one. A bit of resume
of this peculiar issue: the OOM issue is seen on those system with limited memory pool
so we try to increase the memory pool for grub_malloc [2] but hit other (unexpected) issues [3] so
[2] was reverted.

Test Cases

There are two testing scenarios below. For both, please use a testing HW (NEVER on your working desktop/lap) and DISABLE Secure boot (unsigned GRUB binaries for the moment) temporally.

  • Option 1: ISO install (for those that cannot install Fedora due to OOM issues)
    0. Disable Secure boot

    1. Download the ISO [5] which contains the fix, flash it on a USB stick
    2. boot with it your HW. In theory the OOM would be seen here on those particular machines where OOM has been observed before
    3. If possible and your time allows, please install Fedora (use 'On the Network' in the Installation Source menu, this is just
      in case the auto-detect installation media fails). The reason we are asking for full installation is that last time we did not
      testers this step and we ended up with [3].
    4. Reboot your new Fedora System
    5. Follow instructions below (Option 2).
    6. Share your results.

  • Option 2: RPM install (for those already running a Fedora rawhide system)
    0. Disable Secure boot

    1. Boot your system
    2. Download the rpms[4], e.g. koji download-task --arch=x86_64 --arch=noarch 141497105
    3. install the rpms, e.g. sudo dnf install *.rpm
    4. Reboot
    5. Share results

[1] https://src.fedoraproject.org/rpms/grub2/pull-request/207
[2] https://src.fedoraproject.org/rpms/grub2/pull-request/198
[3] https://bugzilla.redhat.com/show_bug.cgi?id=2427945
[4] https://koji.fedoraproject.org/koji/taskinfo?taskID=141497105
[5] https://people.redhat.com/lsandova/oom/boot-efi-alloc-on-verifiers.iso

Prerequisite for the Test Day

  • A bare metal machine (no VM)
  • Download [5] and write it to a USB through Fedora Media Writer
  • Make sure Secure Boot is DISABLE (mokutil --sb-state)

Time Frame

To-be-defined

Test day proposal We have a new fix [1] and hopefully this time would be the final one. A bit of resume of this peculiar issue: the OOM issue is seen on those system with limited memory pool so we try to increase the memory pool for grub_malloc [2] but hit other (unexpected) issues [3] so [2] was reverted. Test Cases There are two testing scenarios below. For both, please use a testing HW (NEVER on your working desktop/lap) and DISABLE Secure boot (unsigned GRUB binaries for the moment) temporally. - Option 1: ISO install (for those that cannot install Fedora due to OOM issues) 0. Disable Secure boot 1. Download the ISO [5] which contains the fix, flash it on a USB stick 3. boot with it your HW. In theory the OOM would be seen here on those particular machines where OOM has been observed before 4. If possible and your time allows, please install Fedora (use 'On the Network' in the Installation Source menu, this is just in case the auto-detect installation media fails). The reason we are asking for full installation is that last time we did not testers this step and we ended up with [3]. 5. Reboot your new Fedora System 6. Follow instructions below (Option 2). 7. Share your results. - Option 2: RPM install (for those already running a Fedora rawhide system) 0. Disable Secure boot 1. Boot your system 2. Download the rpms[4], e.g. koji download-task --arch=x86_64 --arch=noarch 141497105 3. install the rpms, e.g. sudo dnf install *.rpm 4. Reboot 5. Share results [1] https://src.fedoraproject.org/rpms/grub2/pull-request/207 [2] https://src.fedoraproject.org/rpms/grub2/pull-request/198 [3] https://bugzilla.redhat.com/show_bug.cgi?id=2427945 [4] https://koji.fedoraproject.org/koji/taskinfo?taskID=141497105 [5] https://people.redhat.com/lsandova/oom/boot-efi-alloc-on-verifiers.iso Prerequisite for the Test Day - A bare metal machine (no VM) - Download [5] and write it to a USB through Fedora Media Writer - Make sure Secure Boot is DISABLE (mokutil --sb-state) Time Frame To-be-defined
lsandova commented 2026-01-20 19:08:29 +00:00
Author
Copy link

Sorry I forgot to mention before:

For ownership, I believe I need help from the QA team for hosting/organizing the test day.

Sorry I forgot to mention before: For ownership, I believe I need help from the QA team for hosting/organizing the test day.
kparal commented 2026-01-21 09:50:43 +00:00
Owner
Copy link

Metadata Update from @kparal:

  • Custom field story_points adjusted to 2
  • Issue set to the milestone: Fedora 44
  • Issue tagged with: test days
**Metadata Update from @kparal**: - Custom field story_points adjusted to 2 - Issue set to the milestone: Fedora 44 - Issue tagged with: test days
jgroman commented 2026-01-21 11:22:19 +00:00
Owner
Copy link

Metadata Update from @jgroman:

  • Issue assigned to jgroman
**Metadata Update from @jgroman**: - Issue assigned to jgroman
jgroman commented 2026-01-21 11:39:06 +00:00
Owner
Copy link

Hi @lsandova

I'll prepare wiki page and testdays result page for you.

Regarding available dates - how would next week (Jan 26 - Feb 2) work for you?
There are already KDE and Gnome test weeks planned after that. It is not a big problem to have
two testdays to share dates so we could also do that as well.

Thanks!

Hi @lsandova I'll prepare wiki page and testdays result page for you. Regarding available dates - how would next week (Jan 26 - Feb 2) work for you? There are already KDE and Gnome test weeks planned after that. It is not a big problem to have two testdays to share dates so we could also do that as well. Thanks!
lsandova commented 2026-01-21 15:36:50 +00:00
Author
Copy link

Hi @jgroman ,

Hi @lsandova

I'll prepare wiki page and testdays result page for you.

Regarding available dates - how would next week (Jan 26 - Feb 2) work for you?

I talked to the rest of the team and we agreed that we need to wait a bit more until we have a fix and then test both scenarios, the incoming fix and the one mentioned above.

Is it OK if we keep this ticket open for some time ? Hopefully it will not take much.

There are already KDE and Gnome test weeks planned after that. It is not a big problem to have
two testdays to share dates so we could also do that as well.

Thanks!

Hi @jgroman , > Hi @lsandova > > I'll prepare wiki page and testdays result page for you. > > Regarding available dates - how would next week (Jan 26 - Feb 2) work for you? I talked to the rest of the team and we agreed that we need to wait a bit more until we have a fix and then test both scenarios, the incoming fix and the one mentioned above. Is it OK if we keep this ticket open for some time ? Hopefully it will not take much. > There are already KDE and Gnome test weeks planned after that. It is not a big problem to have > two testdays to share dates so we could also do that as well. > > Thanks! >
kparal added this to the Sprint 1 project 2026-01-23 12:46:35 +00:00
lsandova commented 2026-01-26 18:13:36 +00:00
Author
Copy link

@jgroman I have updated the test day description: now we have a solid fix basically.

I have updated several bugzilla tickets asking for testing so we can get some feedback. If all seems ok eg.testers are booting fine, then we set a date. If there is anyone that can't boot, then I need to revisit the issue again :( but I expect this not to happen.

@jgroman I have updated the test day description: now we have a solid fix basically. I have updated several bugzilla tickets asking for testing so we can get some feedback. If all seems ok eg.testers are booting fine, then we set a date. If there is anyone that can't boot, then I need to revisit the issue again :( but I expect this not to happen.
👍 1
adamwill modified the project from Sprint 1 to Sprint 2 2026-01-27 17:38:07 +00:00
lsandova commented 2026-01-30 15:54:29 +00:00
Author
Copy link

@jgroman @kparal unfortunately my plan requesting (before test day starts) some impacted users doing the same test as I am proposing for this test day did not work: no one has tested it or at least nothing has been reported.

Let's try to set a date for this test day and see if we get some traction. Any incoming week is fine, whatever you believe is the best week I am fine with it.

Let me know anything more you need from me or the team.

Thanks for your help.

@jgroman @kparal unfortunately my plan requesting (before test day starts) some impacted users doing the same test as I am proposing for this test day did not work: no one has tested it or at least nothing has been reported. Let's try to set a date for this test day and see if we get some traction. Any incoming week is fine, whatever you believe is the best week I am fine with it. Let me know anything more you need from me or the team. Thanks for your help.
adamwill commented 2026-01-30 16:39:31 +00:00
Owner
Copy link

I've pinged the bug report explicitly NEEDINFO'ing the reporters, and also posted to the discourse thread about the problem. Hopefully that'll shake some testers loose.

I've pinged the bug report explicitly NEEDINFO'ing the reporters, and also [posted to the discourse thread](https://discussion.fedoraproject.org/t/updating-rawhide-today-broke-my-boot-grub/179256/12) about the problem. Hopefully that'll shake some testers loose.
🎉 1
adamwill commented 2026-02-02 16:57:08 +00:00
Owner
Copy link

So we did have one person say the new build works for them - is that enough to go ahead and schedule the event?

So we did have one person [say the new build works for them](https://bugzilla.redhat.com/show_bug.cgi?id=2427945#c36) - is that enough to go ahead and schedule the event?
lsandova commented 2026-02-03 18:20:50 +00:00
Author
Copy link

@adamwill wrote in #862 (comment):

So we did have one person say the new build works for them - is that enough to go ahead and schedule the event?

there is another tester that booted succesfully [2263643#c107] .

I agree with @adamwill , time to move on and organize the test day.

@jgroman let me know something missing from my side.

[2263643#c107] https://bugzilla.redhat.com/show_bug.cgi?id=2263643#c107

@adamwill wrote in https://forge.fedoraproject.org/quality/tickets/issues/862#issuecomment-361312: > So we did have one person [say the new build works for them](https://bugzilla.redhat.com/show_bug.cgi?id=2427945#c36) - is that enough to go ahead and schedule the event? there is another tester that booted succesfully [2263643#c107] . I agree with @adamwill , time to move on and organize the test day. @jgroman let me know something missing from my side. [2263643#c107] https://bugzilla.redhat.com/show_bug.cgi?id=2263643#c107
jgroman commented 2026-02-04 09:36:53 +00:00
Owner
Copy link

Hi @lsandova , would next week (2026-02-09 to 2026-02-15) work for you?
There is a 3 day overlap with GNOME test days but I guess that is not a big problem.
We could also do 2026-02-16 to 2026-02-22 if you wish.

Hi @lsandova , would next week (2026-02-09 to 2026-02-15) work for you? There is a 3 day overlap with GNOME test days but I guess that is not a big problem. We could also do 2026-02-16 to 2026-02-22 if you wish.
lsandova commented 2026-02-04 16:12:07 +00:00
Author
Copy link

@jgroman wrote in #862 (comment):

Hi @lsandova , would next week (2026-02-09 to 2026-02-15) work for you?

Yes, next week is just fine!

There is a 3 day overlap with GNOME test days but I guess that is not a big problem.

it is not. I believe these are two type of testers (user space UI versus bootloader testers), so I doubt dates would interfere.

We could also do 2026-02-16 to 2026-02-22 if you wish.

@jgroman wrote in https://forge.fedoraproject.org/quality/tickets/issues/862#issuecomment-361647: > Hi @lsandova , would next week (2026-02-09 to 2026-02-15) work for you? Yes, next week is just fine! > > There is a 3 day overlap with GNOME test days but I guess that is not a big problem. it is not. I believe these are two type of testers (user space UI versus bootloader testers), so I doubt dates would interfere. > > We could also do 2026-02-16 to 2026-02-22 if you wish.
jgroman commented 2026-02-05 13:25:18 +00:00
Owner
Copy link

Hi Leo @lsandova

I have prepared

Please update the wiki page as necessary, I just copied over "part 1" page for now.
If the testdays result page needs testcase refresh as well I can update that page for you.

Hi Leo @lsandova I have prepared - Test Days wiki page: https://fedoraproject.org/wiki/Test_Day:2026-02-09_GRUB_out_of_memory_fix_verification_part_2 - Test Days App results page: https://testdays.fedoraproject.org/testday/15 - Fedora Calendar Event: https://calendar.fedoraproject.org/QA/2026/2/9/#m11292 Please update the wiki page as necessary, I just copied over "part 1" page for now. If the testdays result page needs testcase refresh as well I can update that page for you.
lsandova commented 2026-02-05 15:30:58 +00:00
Author
Copy link

@jgroman wrote in #862 (comment):

Hi @jgroman ,

Hi Leo @lsandova

I have prepared

This page looks (identical?) as first test day

https://fedoraproject.org/wiki/Test_Day:2025-12-15_GRUB_out_of_memory_verification

but this time we are testing a different fix and different test scenario. Perhaps you pasted the wrong link?

Great, thanks

Please update the wiki page as necessary, I just copied over "part 1" page for now. If the testdays result page needs testcase refresh as well I can update that page for you.

@jgroman wrote in https://forge.fedoraproject.org/quality/tickets/issues/862#issuecomment-372136: Hi @jgroman , > Hi Leo @lsandova > > I have prepared > > * Test Days wiki page: https://fedoraproject.org/wiki/Test_Day:2026-02-09_GRUB_out_of_memory_fix_verification_part_2 This page looks (identical?) as first test day https://fedoraproject.org/wiki/Test_Day:2025-12-15_GRUB_out_of_memory_verification but this time we are testing a different fix and different test scenario. Perhaps you pasted the wrong link? > * Test Days App results page: https://testdays.fedoraproject.org/testday/15 > * Fedora Calendar Event: https://calendar.fedoraproject.org/QA/2026/2/9/#m11292 Great, thanks > Please update the wiki page as necessary, I just copied over "part 1" page for now. If the testdays result page needs testcase refresh as well I can update that page for you.
jgroman commented 2026-02-05 15:34:37 +00:00
Owner
Copy link

This page looks (identical?) as first test day
but this time we are testing a different fix and different test scenario. Perhaps you pasted the wrong link?

Yes, I just copy-pasted the first page content in there as a placeholder.
Please update this page as necessary to fit your current scenario.

> This page looks (identical?) as first test day > but this time we are testing a different fix and different test scenario. Perhaps you pasted the wrong link? Yes, I just copy-pasted the first page content in there as a placeholder. Please update this page as necessary to fit your current scenario.
lsandova commented 2026-02-05 15:41:08 +00:00
Author
Copy link

@jgroman wrote in #862 (comment):

This page looks (identical?) as first test day
but this time we are testing a different fix and different test scenario. Perhaps you pasted the wrong link?

Yes, I just copy-pasted the first page content in there as a placeholder. Please update this page as necessary to fit your current scenario.

Got it! Sure, let me update it now.

@jgroman wrote in https://forge.fedoraproject.org/quality/tickets/issues/862#issuecomment-372150: > > This page looks (identical?) as first test day > > but this time we are testing a different fix and different test scenario. Perhaps you pasted the wrong link? > > Yes, I just copy-pasted the first page content in there as a placeholder. Please update this page as necessary to fit your current scenario. Got it! Sure, let me update it now.
lsandova commented 2026-02-05 18:05:15 +00:00
Author
Copy link

wiki updated https://fedoraproject.org/wiki/Test_Day:2026-02-09_GRUB_out_of_memory_fix_verification_part_2

Please review it and let me know if something is not clear.

wiki updated https://fedoraproject.org/wiki/Test_Day:2026-02-09_GRUB_out_of_memory_fix_verification_part_2 Please review it and let me know if something is not clear.
kparal modified the project from Sprint 2 to Sprint 3 2026-02-10 15:04:47 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
No results found.
Labels
Clear labels   
agile

related to Scrum or other Agile methodology

  
anacondawebui

tickets relating to the anaconda 'web ui' interface refresh

  
arm

   
blockerfe

Issues relating to the blocker / freeze exception process

  
Closed As
Duplicate
Closed with the reason of Duplicate

  
Closed As
Fixed
Closed with the reason of Fixed

  
Closed As
Invalid
Closed with the reason of Invalid

  
Closed As
Wontfix
Closed with the reason of Wontfix

  
Closed As
Worksforme
Closed with the reason of Worksforme

  
coreos

issue related to coreos

  
criteria

release criteria-related issues

  
defect

   
easyfix

   
enhancement

   
iot

Issues related to IoT

  
meeting

a topic for the next QA meeting

  
meta

issues in the issue tracker itself (like, whooooaaa, man)

  
onboarding call

issues that are used to track new contributor onboarding

  
proventesters

   
retrospective

issues filed as a result of QA Retrospective feedback

  
silverblue

Issues related to silverblue

  
sponsor

requests to become a FAS group sponsor

  
test cases

   
test days

   
wiki
  
Backlog Status
Needs Review
Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available.

  
chore

Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

  
documentation

Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

  
points
01
A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

  
Priority
Critical
This is for work that is urgent and of critical importance and so and must be addressed immediately with a higher priority than all other work, even if not originally planned for the current sprint.

  
Priority
High
This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
Priority
Low
This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
Sprint Status
Blocked
Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  
Sprint Status
Done
Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  
Sprint Status
Review
Work items that are complete but need review, testing, or approval before being marked as done.

  
Sprint Status
To Do
Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt

Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

  
Work Item
Bug
Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic
Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
Work Item
Spike
Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  
Work Item
Task
Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

  
Work Item
User Story
User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels
agile
anacondawebui
arm
blockerfe
Closed As
Duplicate
Closed As
Fixed
Closed As
Invalid
Closed As
Wontfix
Closed As
Worksforme
coreos
criteria
defect
easyfix
enhancement
iot
meeting
meta
onboarding call
proventesters
retrospective
silverblue
sponsor
test cases
test days
wiki
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Milestone
Clear milestone
No items
No milestone
Fedora 44
Projects
Clear projects
No items
No project
Sprint 3
Assignees
Clear assignees
No assignees
jgroman
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
quality/tickets#862
No description provided.