2024-02-19 @ 17:00 UTC - Fedora 40 Blocker Review Meeting

Hi folks! It’s time for another blocker review meeting. We have 6 proposed blockers and 1 proposed freeze exception for Beta, and 4 proposed blockers for Final.

The meeting will be on Matrix, as we’re trying to move to more modern systems and the meeting bot is working on Matrix now. 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. 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 weekend and see you on Monday!

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

Meeting started by @adamwill:fedora.im at 17:00:06 UTC

Meeting summary

  1. TOPIC:Roll Call (@adamwill:fedora.im, 17:00:10)
  2. TOPIC:Introduction (@adamwill:fedora.im, 17:06:56)
    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, 17:07:02)
    2. INFO: We'll be following the process outlined at: (@adamwill:fedora.im, 17:07:05)
    3. LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (@adamwill:fedora.im, 17:07:07)
    4. INFO: The bugs up for review today are available at: (@adamwill:fedora.im, 17:07:09)
    5. LINK: http://qa.fedoraproject.org/blockerbugs/current (@adamwill:fedora.im, 17:07:11)
    6. INFO: The criteria for release blocking bugs can be found at: (@adamwill:fedora.im, 17:07:14)
    7. LINK: https://fedoraproject.org/wiki/Basic_Release_Criteria (@adamwill:fedora.im, 17:07:16)
    8. LINK: https://fedoraproject.org/wiki/Fedora_40_Beta_Release_Criteria (@adamwill:fedora.im, 17:07:18)
    9. LINK: https://fedoraproject.org/wiki/Fedora_40_Final_Release_Criteria (@adamwill:fedora.im, 17:07:21)
    10. INFO: for Beta, we have: (@adamwill:fedora.im, 17:07:26)
    11. INFO: 9 Proposed Blockers (@adamwill:fedora.im, 17:07:37)
    12. INFO: 5 Accepted Blockers (@adamwill:fedora.im, 17:07:40)
    13. INFO: 1 Accepted Previous Release Blockers (@adamwill:fedora.im, 17:07:44)
    14. INFO: 1 Proposed Freeze Exceptions (@adamwill:fedora.im, 17:07:47)
    15. INFO: 6 Accepted Freeze Exceptions (@adamwill:fedora.im, 17:07:49)
    16. INFO: for Final, we have: (@adamwill:fedora.im, 17:07:56)
    17. INFO: 4 Proposed Blockers (@adamwill:fedora.im, 17:08:03)
    18. INFO: coremodule will act as secretary (@adamwill:fedora.im, 17:08:12)
  3. TOPIC:Proposed Beta blockers (@adamwill:fedora.im, 17:08:21)
  4. TOPIC:(2264419) webui: non-root btrfs subvolumes are not mounted correctly (@adamwill:fedora.im, 17:08:28)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2264419 (@adamwill:fedora.im, 17:08:31)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1464 (@adamwill:fedora.im, 17:08:33)
    3. INFO: Proposed Blocker, anaconda, POST (@adamwill:fedora.im, 17:08:36)
    4. INFO: Ticket vote: BetaBlocker (+2,0,-0) (+lruzicka, +geraldosimiao) (@adamwill:fedora.im, 17:08:41)
    5. AGREED: 2264419 - AcceptedBlocker (Beta) - this is accepted as a violation of "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", applied to the webui partitioning flow (@adamwill:fedora.im, 17:15:19)
  5. TOPIC:(2263964) Cockpit storage: cannot "Remove a planned storage volume from the planned layout" as required in the release criteria (@adamwill:fedora.im, 17:15:27)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2263964 (@adamwill:fedora.im, 17:15:29)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1459 (@adamwill:fedora.im, 17:15:31)
    3. INFO: Proposed Blocker, distribution, ASSIGNED (@adamwill:fedora.im, 17:15:33)
    4. INFO: Ticket vote: BetaBlocker (+1,1,-1) (+asciiwolf, geraldosimiao, -frantisekz) (@adamwill:fedora.im, 17:15:35)
    5. AGREED: 2263964 - punt (delay decision) - this is clearly a criteria violation, but it is not a straightforward "bug", rather an upstream design choice which was not understood downstream until recently. it is part of an official Change, but was not fully covered in that Change's scope. as this is well outside of the scope of a "bug" process and involves the Change process, we will defer to FESCo's decision on https://pagure.io/fesco/issue/3169 in deciding the status of this bug, and whether to change the release criteria. (@adamwill:fedora.im, 17:33:44)
  6. TOPIC:(2264795) Workstation iso filesystem has incorrect filesystem label (@adamwill:fedora.im, 17:34:01)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2264795 (@adamwill:fedora.im, 17:34:05)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1466 (@adamwill:fedora.im, 17:34:07)
    3. INFO: Proposed Blocker, distribution, NEW (@adamwill:fedora.im, 17:34:10)
    4. INFO: Ticket vote: BetaBlocker (+3,0,-0) (+lruzicka, +geraldosimiao, +sumantrom)' (@adamwill:fedora.im, 17:34:12)
    5. AGREED: 2264795 - RejectedBlocker (Beta) AcceptedFreezeException (Beta) - this is rejected as it concerns an image which is not release-blocking . However, it's accepted as FE on the general principle we accept this kind of issue in non-blocking images as FE instead, but we will only land a fix that could not endanger blocking images (@adamwill:fedora.im, 17:44:19)
  7. TOPIC:(2264415) Raspberry Pi 4 and 400 won't boot into graphical environment (@adamwill:fedora.im, 17:44:26)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2264415 (@adamwill:fedora.im, 17:44:28)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1463 (@adamwill:fedora.im, 17:44:30)
    3. INFO: Proposed Blocker, gdm, NEW (@adamwill:fedora.im, 17:44:34)
    4. INFO: Ticket vote: BetaBlocker (+0,0,-1) (-catanzaro) (@adamwill:fedora.im, 17:44:37)
    5. AGREED: 2264415 - AcceptedBlocker (Beta) - this is accepted as a violation of Basic criterion "Release-blocking ARM disk images must boot to the initial-setup utility" for the ARM Workstation disk image (which is release-blocking) on the Raspberry PI 4 (which is a "supported ARM platform" as defined right above that criterion) (@adamwill:fedora.im, 18:10:15)
    6. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2263952 (@adamwill:fedora.im, 18:10:26)
    7. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1460 (@adamwill:fedora.im, 18:10:28)
    8. INFO: Proposed Blocker, gnome-shell-extension-background-logo, NEW (@adamwill:fedora.im, 18:10:31)
    9. INFO: Ticket vote: BetaBlocker (+4,0,-1) (+asciiwolf, +catanzaro, +geraldosimiao, +lruzicka, -adamwill) (@adamwill:fedora.im, 18:10:33)
    10. INFO: Ticket vote: BetaFreezeException (+1,0,-0) (+asciiwolf) (@adamwill:fedora.im, 18:10:35)
    11. AGREED: 2263952 - punt (delay decision) on blocker status, AcceptedFreezeException (Beta) - the vote for blocker status is split, +4 / -4 at present, with no criterion cited. There is a clear consensus for FE status, however. (@adamwill:fedora.im, 18:22:38)
  8. TOPIC:(2264794) Need to include devcietree files on aarch64 systems iso media (@adamwill:fedora.im, 18:22:45)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2264794 (@adamwill:fedora.im, 18:22:48)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1465 (@adamwill:fedora.im, 18:22:50)
    3. INFO: Proposed Blocker, lorax, NEW (@adamwill:fedora.im, 18:22:53)
    4. AGREED: 2263952 - punt (delay decision) - the report does not explain which images or hardware platforms are affected by this, which seems like required information to make a blocker decision (@adamwill:fedora.im, 18:33:18)
  9. TOPIC:(2264814) AArch64 livemedia creation fails due to running out of space (@adamwill:fedora.im, 18:33:38)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2264814 (@adamwill:fedora.im, 18:33:41)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1467 (@adamwill:fedora.im, 18:33:45)
    3. INFO: Proposed Blocker, lorax, NEW (@adamwill:fedora.im, 18:33:48)
    4. AGREED: 2264814 - RejectedBlocker (Beta) AcceptedFreezeException (Beta) - this concerns an image that is not on the blocking list at https://docs.fedoraproject.org/en-US/releases/f40/blocking/ (the aarch64 Workstation live ISO), so it cannot be a blocker. However, as it's always good for images to build, we do grant an FE (@adamwill:fedora.im, 18:42:18)
  10. TOPIC:(2236356) the software raid disk becomes unusable after click "Rescan" twice (@adamwill:fedora.im, 18:42:29)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2236356 (@adamwill:fedora.im, 18:42:33)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1321 (@adamwill:fedora.im, 18:42:36)
    3. INFO: Proposed Blocker, python-blivet, ASSIGNED (@adamwill:fedora.im, 18:42:39)
    4. INFO: Ticket vote: BetaBlocker (+2,0,-0) (+nielsenb, +geraldosimiao) (@adamwill:fedora.im, 18:42:41)
    5. INFO: Ticket vote: FinalBlocker (+1,0,-0) (+lruzicka) (@adamwill:fedora.im, 18:42:44)
    6. INFO: Ticket vote: BetaFreezeException (+2,0,-0) (+asciiwolf, +lruzicka) (@adamwill:fedora.im, 18:42:46)
    7. AGREED: 2236356 - punt (delay decision) - we're still clarifying exactly the status with f40 here. installer team is also back looking at a fix. we have added a needinfo to the bug (@adamwill:fedora.im, 18:48:04)
  11. TOPIC:(2249392) libblkid returns incomplete information for partitons (e.g. UUID and TYPE are missing) preventing assembly of md raid devices (@adamwill:fedora.im, 18:48:11)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2249392 (@adamwill:fedora.im, 18:48:13)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1446 (@adamwill:fedora.im, 18:48:15)
    3. INFO: Proposed Blocker, util-linux, NEW (@adamwill:fedora.im, 18:48:17)
    4. INFO: Ticket vote: BetaBlocker (+3,0,-0) (+nielsenb, +geraldosimiao, +lruzicka) (@adamwill:fedora.im, 18:48:19)
    5. AGREED: 2249392 - punt (delay decision) - the reporter who reopened this issue may not have the same bug as the original reporter, the situation seems less clear-cut than it was for that reporter. we will delay the decision while attempting to get more information on Sandro's case, including testing on Fedora 40 (@adamwill:fedora.im, 18:57:31)
    6. INFO: we will skip the proposed Final blockers as the meeting is almost at its time limit (@adamwill:fedora.im, 18:58:14)
  12. TOPIC:Open floor (@adamwill:fedora.im, 18:58:17)


Meeting ended at 19:02:05 UTC

Action items

  1. (none)


People present (lines said)

  1. @adamwill:fedora.im (214)
  2. @conan_kudo:matrix.org (54)
  3. @frantisekz:fedora.im (42)
  4. @geraldosimiao:matrix.org (23)
  5. @jkonecny:fedora.im (21)
  6. @kparal:matrix.org (16)
  7. @sumantrom:fedora.im (16)
  8. @zodbot:fedora.im (9)
  9. @marcdeop:matrix.org (6)
  10. @humaton:fedora.im (5)
  11. @meetbot:fedora.im (2)
  12. @coremodule:fedora.im (2)
  13. @pboy:fedora.im (2)
  14. @lruzicka:matrix.org (1)
  15. @davdunc:fedora.im (1)
  16. @amoloney:fedora.im (1)