#549 [dracut] F34/F35 5.14 kernels will not boot on AWS EC2 t2.small / c4.large / m4.large instances | rhbz#2010058
Closed 2 years ago by blockerbot. Opened 2 years ago by blockerbot.

Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2010058
Information from BlockerBugs App:
2010058

Current vote summary

Commented but haven't voted yet: coremodule

The votes have been last counted at 2021-10-18 20:48 UTC and the last processed comment was #comment-758203

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)


So from the bug it's not entirely clear if we have an arch for which there is no single working machine type, and that's all the criteria require. But I'm at least:
FinalFE +1

FinalFE +1

I really want to call this a blocker, but I agree that the applicable criterion is technically met.

FinalFE +1

but in that case we should respin the images with the fix.

AGREED RejectedFinalBlocker
AGREED AcceptedFinalFE

Discussed during the 2021-10-18 blocker review meeting: [0]

The decision to classify this bug as a "RejectedBlocker (Final)" and an "AcceptedFreezeException (Final)" was made as this does not violate the criterion, as we do have at least one working instance type per arch (which is all the criterion requires). But it's clearly a big problem worth fixing for release (and we intend to do so).

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-10-18/f35-blocker-review.2021-10-18-16.00.txt

The following votes have been closed:

Metadata Update from @blockerbot:
- Issue status updated to: Closed (was: Open)

2 years ago

Release F35 is no longer tracked by BlockerBugs, closing this ticket.

Login to comment on this ticket.

Metadata