2024-09-16 @ 16:00 UTC - Fedora 41 Blocker Review Meeting

Hi folks! It’s time for another blocker review meeting. We have 1 proposed blocker for Final.

Here is a handy link which should show you the meeting time in your local time.

The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing.

If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here.

Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you’ll see links labeled “Vote!” next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. This page has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn’t a clear outcome in the ticket voting yet. THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!

We’ll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they’re not fixed. Information on the release criteria for F40 can be found on the wiki.

For more information about the Blocker and Freeze exception process, check out these links:

And for those of you who are curious how a Blocker Review Meeting works - or how it’s supposed to go and you want to run one - check out the SOP on the wiki.

Have a good day and see you tomorrow!

1 Like

Added engineering, release-engineering-team

#blocker-review:fedoraproject.org: F41-blocker-review

Meeting started by @adamwill:fedora.im at 16:00:03 UTC

Meeting summary

  1. TOPIC:Roll Call (@adamwill:fedora.im, 16:00:08)
    1. LINK: https://fedoraproject.org/wiki/Fedora_41_Final_Release_Criteria (@adamwill:fedora.im, 16:04:58)
    2. INFO: Our purpose in this meeting is to review proposed blocker and nice-to-have bugs and decide whether to accept them, and to monitor the progress of fixing existing accepted blocker and nice-to-have bugs. (@adamwill:fedora.im, 16:04:58)
    3. LINK: https://fedoraproject.org/wiki/Basic_Release_Criteria (@adamwill:fedora.im, 16:04:58)
    4. INFO: The criteria for release blocking bugs can be found at: (@adamwill:fedora.im, 16:04:58)
    5. INFO: We'll be following the process outlined at: (@adamwill:fedora.im, 16:04:58)
    6. LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (@adamwill:fedora.im, 16:04:58)
    7. INFO: The bugs up for review today are available at: (@adamwill:fedora.im, 16:04:58)
    8. LINK: http://qa.fedoraproject.org/blockerbugs/current (@adamwill:fedora.im, 16:04:58)
    9. LINK: https://fedoraproject.org/wiki/Fedora_41_Beta_Release_Criteria (@adamwill:fedora.im, 16:04:58)
  2. TOPIC:Introduction (@adamwill:fedora.im, 16:04:58)
    1. INFO: for Final, we have: (@adamwill:fedora.im, 16:05:44)
    2. INFO: 4 Proposed Blockers (@adamwill:fedora.im, 16:05:44)
    3. INFO: 3 Accepted Blockers (@adamwill:fedora.im, 16:05:44)
    4. INFO: František Zatloukal will secretarialize (@adamwill:fedora.im, 16:07:27)
  3. TOPIC:Proposed Final blockers (@adamwill:fedora.im, 16:07:36)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2311936 (@adamwill:fedora.im, 16:07:45)
  4. TOPIC:(2311936) pyanaconda.modules.common.errors.storage.UnknownDeviceError: Volume0_0 (@adamwill:fedora.im, 16:07:45)
    1. INFO: Ticket vote: FinalBlocker (+1,0,-0) (+nielsenb) (@adamwill:fedora.im, 16:07:45)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1658 (@adamwill:fedora.im, 16:07:45)
    3. INFO: Proposed Blocker, anaconda, POST (@adamwill:fedora.im, 16:07:45)
    4. AGREED: 2311936 - AcceptedBlocker (Final) - this is accepted as a clear violation of Final criterion "The installer must be able to detect and install to firmware RAID storage devices" (@adamwill:fedora.im, 16:14:00)
    5. INFO: Ticket vote: FinalBlocker (+1,0,-0) (+nielsenb) (@adamwill:fedora.im, 16:14:08)
    6. INFO: Proposed Blocker, python3.13, NEW (@adamwill:fedora.im, 16:14:08)
    7. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1661 (@adamwill:fedora.im, 16:14:08)
    8. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2311907 (@adamwill:fedora.im, 16:14:08)
  5. TOPIC:(2311907) Anaconda crashes when an error occurs and should be reported. (@adamwill:fedora.im, 16:14:08)
    1. AGREED: 2311907 - AcceptedBlocker (Final) - this is accepted under "Bug hinders execution of required Final test plans or dramatically reduces test coverage" at https://fedoraproject.org/wiki/Fedora_41_Final_Release_Criteria#Final_Blocker_Bugs . this bug prevents us from reliably testing whether crash reporting works, which is an important and release-blocking function (@adamwill:fedora.im, 16:19:32)
    2. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2258100 (@adamwill:fedora.im, 16:19:45)
    3. INFO: Proposed Blocker, qemu, MODIFIED (@adamwill:fedora.im, 16:19:45)
    4. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1663 (@adamwill:fedora.im, 16:19:45)
  6. TOPIC:(2258100) qemu guest agent: migrate "blacklist" option to "block-rpcs", add support for "allow-rpcs" alternative (@adamwill:fedora.im, 16:19:45)
    1. AGREED: 2258100 - AcceptedBlocker (Final) - this is accepted as a violation of Final criterion "All system services present after installation with one of the release-blocking package sets must start properly" on qemu VMs (including cloud instances). we note the affected service provides pretty important functionality for scripted deployment of VMs (@adamwill:fedora.im, 16:38:26)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1662 (@adamwill:fedora.im, 16:38:33)
    3. INFO: Proposed Blocker, wpa_supplicant, NEW (@adamwill:fedora.im, 16:38:33)
  7. TOPIC:(2307226) f41 and rawhide should get the fix from wpa_supplicant-2.11-3.fc40 (@adamwill:fedora.im, 16:38:33)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2307226 (@adamwill:fedora.im, 16:38:33)
    2. AGREED: 2307226 - punt (delay decision) - we agreed to ask for clarification on the seriousness of this issue, as it doesn't seem apparent unless you're an enterprise networking expert (@adamwill:fedora.im, 16:49:02)
  8. TOPIC:Accepted Final blockers (@adamwill:fedora.im, 16:49:20)
    1. INFO: as a reminder, we're checking in on progress here, not revoting (@adamwill:fedora.im, 16:49:29)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1605 (@adamwill:fedora.im, 16:49:37)
  9. TOPIC:(2282171) gsk: vulkan renderer causes gtk4 apps to crash on resize operations on Raspberry Pi 4 and 400 (@adamwill:fedora.im, 16:49:37)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2282171 (@adamwill:fedora.im, 16:49:37)
    2. INFO: Accepted Blocker, bcm283x-firmware, ASSIGNED (@adamwill:fedora.im, 16:49:37)
    3. INFO: peter told me "I know the solution, just need to finish it up and make sure it fully works" (@adamwill:fedora.im, 16:50:01)
    4. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1607 (@adamwill:fedora.im, 16:52:23)
    5. INFO: Accepted Blocker, kernel, ASSIGNED (@adamwill:fedora.im, 16:52:23)
  10. TOPIC:(2283978) Raspberry Pi 4 automatically suspends when idle, claims to support suspend, but can't be woken up (@adamwill:fedora.im, 16:52:23)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2283978 (@adamwill:fedora.im, 16:52:23)
    2. INFO: we've now tagged this as commonbugs, likeliest resolution is that we document this, as fixing it is complex (@adamwill:fedora.im, 16:54:59)
    3. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1603 (@adamwill:fedora.im, 16:56:31)
    4. INFO: Accepted Blocker, selinux-policy, ASSIGNED (@adamwill:fedora.im, 16:56:31)
  11. TOPIC:(2278845) gnome-initial-setup: Choosing avatar results in "SetIconFile call failed" "unknown reason" due to SELinux denial (@adamwill:fedora.im, 16:56:31)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2278845 (@adamwill:fedora.im, 16:56:31)
    2. INFO: we are just waiting for a fix from the selinux maintainer here, not much else to talk about (@adamwill:fedora.im, 16:58:19)
  12. TOPIC:Open floor (@adamwill:fedora.im, 16:58:24)


Meeting ended at 17:02:12 UTC

Action items

  1. (none)


People present (lines said)

  1. @adamwill:fedora.im (115)
  2. @frantisekz:fedora.im (17)
  3. @lruzicka:matrix.org (15)
  4. @nielsenb:fedora.im (13)
  5. @kparal:matrix.org (11)
  6. @zodbot:fedora.im (11)
  7. @conan_kudo:matrix.org (10)
  8. @sumantrom:fedora.im (7)
  9. @derekenz:fedora.im (6)
  10. @siosm:matrix.org (6)
  11. @jkonecny:fedora.im (5)
  12. @farribeiro:matrix.org (3)
  13. @meetbot:fedora.im (2)
  14. @davdunc:fedora.im (2)
  15. @copperi:fedora.im (1)
  16. @jnsamyak:matrix.org (1)
  17. @pboy:fedora.im (1)


1 Like