Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2247873 ** Information from BlockerBugs App:
Commented but haven't voted yet: frantisekz
The votes have been last counted at 2024-02-27 10:47 UTC and the last processed comment was #comment-898181
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
As the Nano is a supported platform and Server is a blocking image, I guess this kinda has to be:
though if it's not technically feasible to fix in time I think it's a reasonable waiver candidate.
Ugh.
Yeah, I agree with you Adam:
Strong waiver candidate, but since pbrobinson said "we almost have a fix for this." fingers crossed here, hopping this fix lands anytime soon.
AGREED AcceptedBetaBlocker
Discussed during the 2024-02-26 blocker review meeting [1]:
"All release-blocking images must boot in their supported configurations." as the affected hardware is a supported platform and Server is a blocking deliverable.
[1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-02-26/f40-blocker-review.2024-02-26-17.01.log.html
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F40 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.