Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2013626 ** Information from BlockerBugs App:
The votes have been last counted at 2021-10-16 00:15 UTC and the last processed comment was #comment-757969
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
FinalBlocker +1 This is a clear violation of the cited criterion and it appears to be widespread, as mattia noted. It seems like this may be fixed in 5.23.
FinalBlocker +1
This is a clear violation of the cited criterion and it appears to be widespread, as mattia noted. It seems like this may be fixed in 5.23.
FinalBlocker -1
As per my findings ( https://bugzilla.redhat.com/show_bug.cgi?id=2013626#c5 and https://bugzilla.redhat.com/show_bug.cgi?id=2013626#c11 ) and @lruzicka 's ( https://bugzilla.redhat.com/show_bug.cgi?id=2013626#c10 ), it doesn't seem to affect vast majority of the hardware.
Changing my previous vote based on the limited scope of the affected platforms.
My opinion, because it's not a regression (I have the same problem in F34 also).
FinalBlocker -1 Since it doesn't seem to reproduce in many situations, on further testing.
Oh, you have stolen my blocker.
AGREED RejectedFinalBlocker
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F35 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.