Fedora Linux 39 Beta blocker status summary #1

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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: @adamw@xxxxxxxxxxxxx
https://www.happyassassin.net
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux