2025-03-17 @ 16:00 UTC - Fedora 42 Blocker Review Meeting

Project Discussion
, ,
1

Hi folks! It’s time for a Fedora 42 blocker review meeting! We have 5 proposed blockers for Final.

Note that as clocks went forward in North America recently, the meeting is now at 1600 UTC. If you changed your clocks this weekend, the meeting will be at the same local time as before. If you didn’t, the meeting will be an hour earlier in your local time.

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 this weekend, 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. Overview - fedora-qa/blocker-review - Pagure.io 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 F42 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 weekend and see you on Monday!

1 Like
2

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

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

Meeting summary

  1. TOPIC:Roll Call (@adamwill:fedora.im, 16:01:03)
    1. LINK: https://fedoraproject.org/wiki/Basic_Release_Criteria (@adamwill:fedora.im, 16:05:04)
    2. INFO: We'll be following the process outlined at: (@adamwill:fedora.im, 16:05:04)
  2. TOPIC:Introduction (@adamwill:fedora.im, 16:05:04)
    1. 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:05:04)
    2. LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (@adamwill:fedora.im, 16:05:04)
    3. INFO: The bugs up for review today are available at: (@adamwill:fedora.im, 16:05:04)
    4. LINK: http://qa.fedoraproject.org/blockerbugs/current (@adamwill:fedora.im, 16:05:04)
    5. INFO: The criteria for release blocking bugs can be found at: (@adamwill:fedora.im, 16:05:04)
    6. LINK: https://fedoraproject.org/wiki/Fedora_42_Beta_Release_Criteria (@adamwill:fedora.im, 16:05:04)
    7. LINK: https://fedoraproject.org/wiki/Fedora_42_Final_Release_Criteria (@adamwill:fedora.im, 16:05:04)
    8. INFO: for Final, we have: (@adamwill:fedora.im, 16:05:21)
    9. INFO: 5 Accepted Blockers (@adamwill:fedora.im, 16:05:22)
    10. INFO: 4 Proposed Blockers (@adamwill:fedora.im, 16:05:22)
    11. INFO: 1 Proposed Freeze Exceptions (@adamwill:fedora.im, 16:05:27)
    12. INFO: 1 Accepted Freeze Exceptions (@adamwill:fedora.im, 16:05:27)
    13. INFO: lbrabec will secretarialize (@adamwill:fedora.im, 16:09:48)
    14. INFO: Proposed Blocker, anaconda-webui, ASSIGNED (@adamwill:fedora.im, 16:11:17)
    15. INFO: Ticket vote: FinalBlocker (+3,0,-0) (+nielsenb, +derekenz, +geraldosimiao) (@adamwill:fedora.im, 16:11:17)
  3. TOPIC:(2352573) Can't choose a bootloader device, crash when biosboot partition is on the second one (@adamwill:fedora.im, 16:11:17)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2352573 (@adamwill:fedora.im, 16:11:17)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1798 (@adamwill:fedora.im, 16:11:17)
    3. AGREED: 2352573 - AcceptedBlocker (Final) - this is accepted as a violation of "Reject or disallow invalid disk and volume configurations without crashing". We agree that, for webUI, it will be satisfactory if it correctly prevents the user from attempting this configuration, rather than allowing the user to proceed and crashing. We consider the ability to do this in gtkUI to fulfill the requirement that this operation be possible, so we do not require webUI to implement it for F42 (@adamwill:fedora.im, 16:20:30)
  4. TOPIC:(2351848) unable to perform an mdraid installation with Fedora-Workstation-Live-42_Beta-1.4.x86_64.iso (@adamwill:fedora.im, 16:21:23)
    1. INFO: Ticket vote: FinalBlocker (+4,0,-0) (+nielsenb, +boniboyblue, +geraldosimiao, +derekenz) (@adamwill:fedora.im, 16:21:23)
    2. INFO: Proposed Blocker, anaconda, ON_QA (@adamwill:fedora.im, 16:21:23)
    3. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1792 (@adamwill:fedora.im, 16:21:23)
    4. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2351848 (@adamwill:fedora.im, 16:21:23)
    5. AGREED: 2351848 - AcceptedBlocker (Final) - this is accepted as a conditional violation of "Assign mount points to existing storage volumes", in the case that you're using webUI and the 'existing storage volume' is a RAID device (possibly only one you just created in the storage editor) (@adamwill:fedora.im, 16:31:14)
    6. INFO: Proposed Blocker, grub2, ON_QA (@adamwill:fedora.im, 16:31:35)
    7. INFO: Ticket vote: FinalBlocker (+4,0,-0) (+nielsenb, +lruzicka, +derekenz, +geraldosimiao) (@adamwill:fedora.im, 16:31:35)
    8. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2351559 (@adamwill:fedora.im, 16:31:35)
    9. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1789 (@adamwill:fedora.im, 16:31:35)
  5. TOPIC:(2351559) Grub cannot boot Windows on a dual boot installation. (@adamwill:fedora.im, 16:31:35)
    1. AGREED: 2351559 - AcceptedBlocker (Final) - this is accepted as a violation of "The installer must be able to install into free space alongside an existing clean Windows installation. As long as the Windows installation does not have BitLocker enabled, the installer must also install a bootloader which can boot into both Windows and Fedora" (@adamwill:fedora.im, 16:35:43)
    2. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2352715 (@adamwill:fedora.im, 16:37:01)
    3. INFO: Ticket vote: FinalBlocker (+0,0,-3) (-catanzaro, -nielsenb, -boniboyblue) (@adamwill:fedora.im, 16:37:01)
    4. INFO: Proposed Blocker, gtk4, NEW (@adamwill:fedora.im, 16:37:01)
    5. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1795 (@adamwill:fedora.im, 16:37:01)
  6. TOPIC:(2352715) [abrt] nautilus: wsi_common_acquire_next_image2(): nautilus killed by SIGSEGV (@adamwill:fedora.im, 16:37:01)
    1. AGREED: 2352715 - RejectedBlocker (Final) - this is rejected for now as nobody has been able to reproduce it, so it doesn't seem like a common enough crash to be a conditional criteria violation. We can re-consider it if somebody is able to reproduce, or if feedback from upstream indicates it may affect a substantial number of users (@adamwill:fedora.im, 16:45:19)
    2. INFO: that's all the blocker proposals (@adamwill:fedora.im, 16:45:52)
  7. TOPIC:Proposed Final freeze exceptions (@adamwill:fedora.im, 16:46:00)
    1. INFO: Ticket vote: FinalBlocker (+0,0,-4) (-kashyapc, -nielsenb, -derekenz, -geraldosimiao) (@adamwill:fedora.im, 16:46:05)
  8. TOPIC:(2352385) unable to reuse the btrfs-formatted disks for other filesystems (@adamwill:fedora.im, 16:46:05)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2352385 (@adamwill:fedora.im, 16:46:05)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1793 (@adamwill:fedora.im, 16:46:05)
    3. INFO: Proposed Freeze Exceptions, cockpit, POST (@adamwill:fedora.im, 16:46:05)
    4. AGREED: 2352385 - AcceptedFreezeException (Final) - this is accepted as an FE as it's a desirable feature that it would be good to get into F42 if we can land it in enough time to test it. we won't take it very late during freeze (@adamwill:fedora.im, 16:52:15)
    5. INFO: that's all the proposals (@adamwill:fedora.im, 16:52:50)
  9. TOPIC:Accepted Final blockers (@adamwill:fedora.im, 16:52:59)
  10. TOPIC:(2351026) UI partly in English when 100% translated (@adamwill:fedora.im, 16:53:21)
    1. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1796 (@adamwill:fedora.im, 16:53:21)
    2. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2351026 (@adamwill:fedora.im, 16:53:21)
    3. INFO: Accepted Blocker, anaconda-webui, POST (@adamwill:fedora.im, 16:53:21)
    4. INFO: anaconda team will put the full, correct strings in weblate, then it's over to translators to do the translations, we'll just hope as much as possible gets into the final f42 anaconda build (@adamwill:fedora.im, 16:54:48)
    5. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1794 (@adamwill:fedora.im, 16:56:27)
    6. INFO: Accepted Blocker, distribution, NEW (@adamwill:fedora.im, 16:56:27)
    7. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2352679 (@adamwill:fedora.im, 16:56:27)
  11. TOPIC:(2352679) Fedora 42: Server boot aarch64 image exceeds maximum size (@adamwill:fedora.im, 16:56:27)
    1. ACTION: adamw to poke server WG about investigating this one and/or bumping the target size (@adamwill:fedora.im, 16:59:48)
  12. TOPIC:(2349314) Keyring fails to unlock on startup (@adamwill:fedora.im, 17:00:36)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2349314 (@adamwill:fedora.im, 17:00:36)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1774 (@adamwill:fedora.im, 17:00:36)
    3. INFO: Accepted Blocker, gnome-keyring, POST (@adamwill:fedora.im, 17:00:36)
    4. ACTION: adamw to backport the proposed (but somehow stalled) upstream fix for this so we can see if it changes how commonly folks are seeing cases of this problem (@adamwill:fedora.im, 17:07:31)
    5. INFO: Accepted Blocker, mdadm, ASSIGNED (@adamwill:fedora.im, 17:10:41)
  13. TOPIC:(2325906) [live] Can't reuse existing RAID partitioning (@adamwill:fedora.im, 17:10:41)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2325906 (@adamwill:fedora.im, 17:10:41)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1790 (@adamwill:fedora.im, 17:10:41)
    3. INFO: we are waiting on developers here. mdadm maintainer has not responded, this may need some poking. we might also need to consider working around the issue at anaconda/blivet level (@adamwill:fedora.im, 17:16:14)
    4. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1765 (@adamwill:fedora.im, 17:16:24)
    5. INFO: Accepted Blocker, plasma-welcome-fedora, NEW (@adamwill:fedora.im, 17:16:24)
    6. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2347292 (@adamwill:fedora.im, 17:16:24)
  14. TOPIC:(2347292) The initial setup in KDE does not switch on third party repositories (@adamwill:fedora.im, 17:16:24)
    1. ACTION: lruzicka to re-test this and either confirm it's fixed or provide a clear reproducer for KDE team (@adamwill:fedora.im, 17:18:41)
  15. TOPIC:Open floor (@adamwill:fedora.im, 17:21:24)


Meeting ended at 17:26:00 UTC

Action items

  1. adamw to poke server WG about investigating this one and/or bumping the target size
  2. adamw to backport the proposed (but somehow stalled) upstream fix for this so we can see if it changes how commonly folks are seeing cases of this problem
  3. lruzicka to re-test this and either confirm it's fixed or provide a clear reproducer for KDE team


People present (lines said)

  1. @adamwill:fedora.im (165)
  2. @kparal:matrix.org (25)
  3. @nielsenb:fedora.im (19)
  4. @derekenz:fedora.im (19)
  5. @geraldosimiao:matrix.org (15)
  6. @zodbot:fedora.im (15)
  7. @jkonecny:fedora.im (10)
  8. @lruzicka:matrix.org (10)
  9. @boniboyblue:fedora.im (9)
  10. @tablepc:fedora.im (8)
  11. @kashyapc:fedora.im (7)
  12. @farribeiro:matrix.org (7)
  13. @conan_kudo:matrix.org (7)
  14. @lbrabec:matrix.org (6)
  15. @meetbot:fedora.im (2)
  16. @jnsamyak:matrix.org (1)
  17. @siosm:matrix.org (1)


1 Like