Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2001135 ** Information from BlockerBugs App:
The votes have been last counted at 2021-10-07 22:54 UTC and the last processed comment was #comment-756916
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
I'm assuming that for some people this happens a lot (>50% of cases), as mentioned in the bug report. It didn't happen to me that often personally. It this was a rare occurrence and there was no other complication, I'd be FinalBlocker 0.
FinalBlocker 0
It happens quite a lot in openQA, and happens to me quite a lot in local VM testing. I suspect it happens more often the slower the system is, but that's just speculation. Still, overall I think I'm a moderate:
on what we know ATM. Since it's a slightly tough call I'm not going mark it accepted with that bare +3, let's give a bit more chance for disagreement. However, can I ask you both - @bcotton @kparal (or anyone else) to quickly vote on FE as well, so we can accept it as an FE and then we have basis to take the fix without waiting for more blocker votes if necessary? Thanks! I am:
FinalFE +1
FinalBlocker +1 FinalFE +1
OK, I think +5 is enough to accept it as a blocker.
AGREED AcceptedFinalBlocker
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.