Fedora Linux 39 Beta blocker status summary #1
Hi folks! Sorry for not sending these sooner, but better late than never: here's a blocker bug status summary for Fedora 39. We're currently targeting a go/no-go meeting this Thursday (September 14) and release the following Tuesday (September 19). Action summary == Accepted blockers - 1. anaconda - webUI: cannot install to encrypted software RAID partition - POST: anaconda team to send new release/build 2. kernel - /dev/tpm* is missing with new kernels - VERIFIED: releng and I to push the fix stable 3. shim - Live image made with BOOTX64.EFI from latest shim-x64-15.6-2 fails to boot on some boards - NEW: likely waive again at go/no-go Proposed blockers - 1. anaconda - Anaconda webUI can't handle two volumes with the same LABEL, writes into a different partition than indicated - NEW: anaconda team to investigate and fix 2. edk2 - Fedora 39 fails to boot on qemu VM using OVMF_CODE.secboot.fd firmware - NEW: QA to isolate the bug more precisely, kraxel to investigate and fix 3. fedora-repos - updates-testing is not enabled when it should be - VERIFIED: releng and I to push the fix stable 4. python-blivet - blivet-gui creates different volumes with the same name, confusing anaconda webUI - ASSIGNED: blivet team to investigate and fix Bug-by-bug detail = Accepted blockers - 1. anaconda - webUI: cannot install to encrypted software RAID partition - POST There is a fix for this which has been verified. We need a new anaconda build with it included (anaconda team). 2. kernel - /dev/tpm* is missing with new kernels - VERIFIED This just needs to be pushed to stable (me and releng). 3. shim - Live image made with BOOTX64.EFI from latest shim-x64-15.6-2 fails to boot on some boards - NEW It seems that, unfortunately, we may have to waive this *again*. There is definite movement upstream but it probably hasn't moved far enough to let us fix it for Beta. We're hoping to finally have this resolved for Final. Proposed blockers - 1. anaconda - Anaconda webUI can't handle two volumes with the same LABEL, writes into a different partition than indicated - NEW It's possible to have multiple btrfs volumes with the same label, which confuses anaconda/blivet and can result in data getting written to a different place than indicated. Seems likely to be accepted as a blocker, we need anaconda/blivet folks to look at fixing this (anaconda team). 2. edk2 - Fedora 39 fails to boot on qemu VM using OVMF_CODE.secboot.fd firmware - NEW This was initially filed and proposed on the basis that VM boot didn't work at all, but then we discovered it was specific to the Secure Boot- enabled UEFI firmware configuration. That may not be important enough to merit blocker status, but we should definitely look into exactly what the trigger is between host and guest, and get the edk2 maintainers to look into this (kraxel). 3. fedora-repos - updates-testing is not enabled when it should be - VERIFIED It's an interesting question whether the criteria do or should cover this, but the fix is already accepted as an FE and queued for stable, so it will be pushed shortly (me and releng). 4. python-blivet - blivet-gui creates different volumes with the same name, confusing anaconda webUI - ASSIGNED This is kinda a companion to 1: not only can multiple btrfs volumes with the same label exist, but blivet actually creates them this way at present unless you explicitly set a label. There's a question whether resolving this would be enough to make 1. not a blocker, or whether we should still block on 1. because other tools could potentially create the same situation. Either way, we want blivet devs to fix this, ideally (vtrefny). -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2023-09-11 @ 16:00 UTC - Fedora 39 Blocker Review Meeting
# F39 Blocker Review meeting # Date: 2023-09-11 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.libera.chat (*NOT* Matrix) Hi folks! We have 4 proposed Beta blockers, 5 proposed Beta freeze exception issues and 4 proposed Final blockers to review, so let's have a meeting tomorrow. The meeting will on IRC only due to the ongoing lack of a Matrix <-> IRC bridge and a meeting bot on the Matrix side. If you no longer have an IRC setup you can join via webIRC: https://web.libera.chat/ , enter a nickname and put #fedora-blocker-review in the Channel box. If you have time tonight, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . 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. https://pagure.io/fedora-qa/blocker-review 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 F39 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process 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: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] Kernel 6.5 Test Week 2023-09-10 to 2023-09-17
Hey All, I would like to invite all of you to participate in the Kernel 6.5 Test week is happening from 2023-09-10 to 2023-09-17. It's fairly simple, head over to the wiki [0] and read in detail about the test week and simply run the test case mentioned in[1] and enter your results. As usual, the Fedora QA team will hangout at #fedora-test-...@libera.chat for questions and discussion. [0] http://fedoraproject.org/wiki/Test_Day:2023-09-10_Kernel_6.5_Test_Week [1] https://testdays.fedoraproject.org/events/166 -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Kernel 6.5 Test Week 2023-09-10 to 2023-09-17
Hey All, I would like to invite all of you to participate in the Kernel 6.5 Test week is happening from 2023-09-10 to 2023-09-17. It's fairly simple, head over to the wiki [0] and read in detail about the test week and simply run the test case mentioned in[1] and enter your results. As usual, the Fedora QA team will hangout at #fedora-test-...@libera.chat for questions and discussion. [0] http://fedoraproject.org/wiki/Test_Day:2023-09-10_Kernel_6.5_Test_Week [1] https://testdays.fedoraproject.org/events/166 -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
