2025-03-31 @ 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 4 proposed blockers and 2 proposed freeze exceptions 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 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
3

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

Meeting started by @adamwill:fedora.im at 16:01:08 UTC

Meeting summary

  1. TOPIC:Roll Call (@adamwill:fedora.im, 16:01:12)
  2. TOPIC:Introduction (@adamwill:fedora.im, 16:05:39)
    1. INFO: The criteria for release blocking bugs can be found at: (@adamwill:fedora.im, 16:05:39)
    2. LINK: https://fedoraproject.org/wiki/Fedora_42_Final_Release_Criteria (@adamwill:fedora.im, 16:05:39)
    3. LINK: https://fedoraproject.org/wiki/Fedora_42_Beta_Release_Criteria (@adamwill:fedora.im, 16:05:39)
    4. LINK: http://qa.fedoraproject.org/blockerbugs/current (@adamwill:fedora.im, 16:05:39)
    5. INFO: The bugs up for review today are available at: (@adamwill:fedora.im, 16:05:39)
    6. LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (@adamwill:fedora.im, 16:05:39)
    7. INFO: We'll be following the process outlined at: (@adamwill:fedora.im, 16:05:39)
    8. LINK: https://fedoraproject.org/wiki/Basic_Release_Criteria (@adamwill:fedora.im, 16:05:39)
    9. 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:39)
    10. INFO: for F42 Final, we have: (@adamwill:fedora.im, 16:06:06)
    11. INFO: 8 Accepted Blockers (@adamwill:fedora.im, 16:06:07)
    12. INFO: 3 Proposed Blockers (@adamwill:fedora.im, 16:06:07)
    13. INFO: 2 Accepted Freeze Exceptions (@adamwill:fedora.im, 16:06:11)
    14. INFO: 1 Proposed Freeze Exceptions (@adamwill:fedora.im, 16:06:11)
    15. INFO: adamw will secretarialize (@adamwill:fedora.im, 16:09:38)
  3. TOPIC:Proposed Final blockers (@adamwill:fedora.im, 16:09:54)
    1. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1817 (@adamwill:fedora.im, 16:10:02)
    2. INFO: Proposed Blocker, abrt, NEW (@adamwill:fedora.im, 16:10:02)
  4. TOPIC:(2356237) "Package isn't signed with proper key" for all packages (@adamwill:fedora.im, 16:10:02)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2356237 (@adamwill:fedora.im, 16:10:02)
    2. INFO: in a late substitution, Lukas Brabec will secretarialize (@adamwill:fedora.im, 16:12:55)
    3. AGREED: 2356237 - RejectedBlocker (Final) - this appears to have been a blip with unsigned packages appearing in a single ISO in a single compose. If we see it repeat, or figure out the cause and decide it endangers the official compose, we will re-consider this. We will check this in all RC releases before signing off (@adamwill:fedora.im, 16:39:43)
    4. INFO: Ticket vote: FinalBlocker (+4,0,-0) (+geraldosimiao, +boniboyblue, +derekenz, +nielsenb) (@adamwill:fedora.im, 16:40:08)
    5. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2354798 (@adamwill:fedora.im, 16:40:08)
  5. TOPIC:(2354798) "no usable disks" after re-creating MDRAID (@adamwill:fedora.im, 16:40:08)
    1. INFO: Proposed Blocker, anaconda, NEW (@adamwill:fedora.im, 16:40:08)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1809 (@adamwill:fedora.im, 16:40:08)
    3. AGREED: 2354798 - AcceptedBlocker (Final) - this is accepted as a violation of Beta custom partition criterion "...the installer must be able to: Correctly interpret, and modify as described below ... software RAID arrays at RAID levels 0, 1 and 5 containing ext4 partitions ... Remove existing storage volumes ... Create mount points backed by ext4 partitions, LVM volumes or btrfs volumes, or software RAID arrays at RAID levels 0, 1 and 5 containing ext4 partitions" (@adamwill:fedora.im, 16:54:35)
    4. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1818 (@adamwill:fedora.im, 16:54:52)
  6. TOPIC:(2356257) Can't open settings to adjust Bugzilla apikey (@adamwill:fedora.im, 16:54:52)
    1. INFO: Proposed Blocker, gnome-abrt, NEW (@adamwill:fedora.im, 16:54:52)
    2. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2356257 (@adamwill:fedora.im, 16:54:52)
    3. AGREED: 2356257 - AcceptedBlocker (Final) - this is accepted as a conditional violation of the Final criterion requiring preinstalled apps on Workstation to "start successfully and withstand a basic functionality test", with the Beta upgrade criterion also relevant. We agreed this bug renders the app effectively useless if an invalid API key is set, and there are enough scenarios where that may be the case - e.g. a typo or a previously-valid key on an upgraded system which has now expired - to accept this as a blocker (@adamwill:fedora.im, 17:25:03)
    4. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2355033 (@adamwill:fedora.im, 17:25:28)
    5. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1813 (@adamwill:fedora.im, 17:25:28)
  7. TOPIC:(2355033) Fedora 42 beta unable to shutdown despite "No inhibitors" (@adamwill:fedora.im, 17:25:28)
    1. INFO: Ticket vote: FinalBlocker (+1,0,-5) (+augenauf, -boniboyblue, -derekenz, -geraldosimiao, -nielsenb, -lruzicka) (@adamwill:fedora.im, 17:25:28)
    2. INFO: Proposed Blocker, gnome-shell, NEW (@adamwill:fedora.im, 17:25:28)
    3. INFO: Ticket vote: FinalFreezeException (+4,0,-0) (+boniboyblue, +asciiwolf, +nielsenb, +lruzicka) (@adamwill:fedora.im, 17:25:28)
    4. AGREED: 2355033 - punt (delay decision) on blocker status, AcceptedFreezeException (Final) - after some discussion of the details behind this bug, we're not sure whether to block on it. The worst case is when something not tracked by GNOME is inhibiting shutdown; in this case, shutdown fails without explanation. But that will not usually be the case, and in at least some cases, the new behaviour is probably better than the old behaviour (e.g. it wasn't good that you could happily shut down while a package install operation was happening outside of GNOME). we will punt this to try and investigate specific triggers to aid in deciding whether to block. It's clearly desirable to improve this behaviour during freeze if we can, though, so this is accepted FE. (@adamwill:fedora.im, 18:04:09)
    5. INFO: that's all the proposals (that last one was the only outstanding proposed FE) (@adamwill:fedora.im, 18:04:39)
  8. TOPIC:Accepted Final blockers (@adamwill:fedora.im, 18:04:51)
    1. INFO: Accepted Blocker, anaconda, POST (@adamwill:fedora.im, 18:05:15)
  9. TOPIC:(2354805) putting /boot on MDRAID0 is accepted and results in a non-booting system (@adamwill:fedora.im, 18:05:15)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2354805 (@adamwill:fedora.im, 18:05:15)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1810 (@adamwill:fedora.im, 18:05:15)
    3. INFO: this is in POST so we're waiting on a new anaconda build to test (@adamwill:fedora.im, 18:05:27)
  10. TOPIC:(2353002) webui does not support MBR disks, but doesn't properly communicate this, instead e.g. requires biosboot partition even though that is impossible (@adamwill:fedora.im, 18:05:44)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2353002 (@adamwill:fedora.im, 18:05:44)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1804 (@adamwill:fedora.im, 18:05:44)
    3. INFO: Accepted Blocker, anaconda-webui, ASSIGNED (@adamwill:fedora.im, 18:05:44)
    4. INFO: a fix for this was attempted, but testing seems to indicate it's still broken, we will wait to hear back from anaconda team (@adamwill:fedora.im, 18:09:54)
    5. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2352679 (@adamwill:fedora.im, 18:10:02)
    6. INFO: Accepted Blocker, distribution, ASSIGNED (@adamwill:fedora.im, 18:10:02)
    7. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1794 (@adamwill:fedora.im, 18:10:02)
  11. TOPIC:(2352679) Fedora 42: Server boot aarch64 image exceeds maximum size (@adamwill:fedora.im, 18:10:02)
    1. INFO: adamw sent a patch for dracut which would get this *nearly* back under size but not quite (@adamwill:fedora.im, 18:10:17)
    2. INFO: we can try to trim a bit more, or just bump the target size (@adamwill:fedora.im, 18:10:25)
    3. INFO: adamw sent a patch for lorax which would get this *nearly* back under size but not quite (@adamwill:fedora.im, 18:10:43)
    4. INFO: Accepted Blocker, fedora-repos, NEW (@adamwill:fedora.im, 18:12:36)
    5. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1816 (@adamwill:fedora.im, 18:12:36)
  12. TOPIC:(2356173) updates-testing needs to be disabled for F42 GA (@adamwill:fedora.im, 18:12:36)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2356173 (@adamwill:fedora.im, 18:12:36)
    2. INFO: this is pretty straightforward, just waiting for a maintainer to do the new build (@adamwill:fedora.im, 18:13:01)
    3. INFO: Accepted Blocker, mdadm, POST (@adamwill:fedora.im, 18:13:10)
    4. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1790 (@adamwill:fedora.im, 18:13:10)
    5. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2325906 (@adamwill:fedora.im, 18:13:10)
  13. TOPIC:(2325906) [live] Can't reuse existing RAID partitioning (@adamwill:fedora.im, 18:13:10)
    1. INFO: we have a potential fix for this, but it's encountering pushback upstream, trying to get that resolved before backporting it (@adamwill:fedora.im, 18:14:42)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1807 (@adamwill:fedora.im, 18:16:13)
  14. TOPIC:(2354592) GNOME crashes on startup if keyboard accessibility features are enabled (@adamwill:fedora.im, 18:16:13)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2354592 (@adamwill:fedora.im, 18:16:13)
    2. INFO: Accepted Blocker, mutter, POST (@adamwill:fedora.im, 18:16:13)
    3. INFO: the fix for this is done and tested and will be part of an imminent mutter 48.1 which should show up in fedora soon after release (@adamwill:fedora.im, 18:18:32)
  15. TOPIC:(2354865) repo states are not synchronized between DNF5 and PackageKit (GUI package managers), because of repo overrides (@adamwill:fedora.im, 18:18:44)
    1. INFO: Accepted Blocker, PackageKit, NEW (@adamwill:fedora.im, 18:18:44)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1812 (@adamwill:fedora.im, 18:18:44)
    3. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2354865 (@adamwill:fedora.im, 18:18:44)
    4. INFO: we'll get dnf developers' input on this, but it's a high risk not to be fixable within the release time frame, we may have to waive it (@adamwill:fedora.im, 18:21:51)
    5. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1814 (@adamwill:fedora.im, 18:25:14)
    6. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2355207 (@adamwill:fedora.im, 18:25:14)
  16. TOPIC:(2355207) Remote install via RDP fails (client either drops connection immediately or hangs at a white screen) since Fedora-42-20250316.n.0 (@adamwill:fedora.im, 18:25:14)
    1. INFO: Accepted Blocker, pipewire, POST (@adamwill:fedora.im, 18:25:14)
    2. INFO: fix for this is pending, just needs a bit of a tweak on PR review, should land soon (@adamwill:fedora.im, 18:25:56)
  17. TOPIC:Open floor (@adamwill:fedora.im, 18:27:31)


Meeting ended at 18:33:00 UTC

Action items

  1. (none)


People present (lines said)

  1. @adamwill:fedora.im (261)
  2. @kparal:matrix.org (104)
  3. @geraldosimiao:matrix.org (89)
  4. @lruzicka:matrix.org (28)
  5. @boniboyblue:fedora.im (16)
  6. @conan_kudo:matrix.org (16)
  7. @derekenz:fedora.im (13)
  8. @aggraxis:fedora.im (8)
  9. @farribeiro:matrix.org (8)
  10. @zodbot:fedora.im (8)
  11. @matthiasc:gnome.org (6)
  12. @lbrabec:matrix.org (5)
  13. @nirik:matrix.scrye.com (5)
  14. @salimma:fedora.im (3)
  15. @meetbot:fedora.im (2)
  16. @decathorpe:fedora.im (1)


1 Like