Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2131183 ** Information from BlockerBugs App:
Commented but haven't voted yet: frantisekz
The votes have been last counted at 2022-10-03 17:10 UTC and the last processed comment was #comment-819714
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
"Hit or miss, maybe every 2 out of 3 attempts it will crash." is pretty frequent. If it happens that there is some weird circumstance and it's more rare or avoidable after all, but given the info we've got, definitely a blocker.
Both me and Kamil couldn't reproduce that bug. I'm not really sure what to think about it.
I think I'd rather err on the side of caution here, and accept it, until we have more info from developers. If it turns out to be a very niche corner case, we can reconsider the blocker status.
For the reasons given by @mattdm and @kparal.
Great news on the bug ticket: "Fixed in a pull request: https://github.com/rhinstaller/anaconda/pull/4359 "
So, to make sure the fix arrives at stable it can be a blocker or just a FE. I vote both just in case.
FinalBlocker +1 FinalFE +1
AGREED AcceptedFinalBlocker
Discussed during the 2022-10-03 blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2022-10-03/f37-blocker-review.2022-10-03-16.00.log.txt
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F37 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.