Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2232838 ** Information from BlockerBugs App:
Commented but haven't voted yet: kparal, coremodule
The votes have been last counted at 2023-09-11 18:11 UTC and the last processed comment was #comment-873633
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)
BetaBlocker +1
BetaBlocker
FinalBlocker
BetaFE
FinalFE
0Day
PreviousRelease
+1
0
-1
It's going to be difficult to estimate the number of affected users. And it seems that unfortunately kernel devs haven't even yet started working on resolving it. Also, it already affects all our users, including stable releases. So I see only one benefit in blocking the F39 release on this - we would make sure that F39 would be installable on these PCs. If we wouldn't block and the fixed kernel would arrive a week or two later, users would have to wait for F40 (or install F38 and upgrade). All of this of course assumes there will be some fix ready in the upcoming weeks (or we can revert the identified commit and carry it downstream, not sure if that's an approach we want to take).
I think that a condition that makes a uninstallable system is a final blocker (not to say beta too).
FinalBlocker +1
AGREED AcceptedBetaBlocker
Discussed during the 2023-09-11 blocker review meeting: [0]
The decision to classify this bug as an "AcceptedBlocker (Beta)" was made as it violates the following criterion:
"The installer must be able to complete an installation to a single disk" and/or "A system installed with a release-blocking desktop must boot to a log in screen" on affected systems (whichever point it fails at).
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2023-09-11/f39-blocker-review.2023-09-11-16.00.txt
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F39 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.