Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2316058 ** Information from BlockerBugs App:
Commented but haven't voted yet: kparal, adamwill
The votes have been last counted at 2024-10-07 15:57 UTC and the last processed comment was #comment-937164
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
A new iteration of an older bug, but I am still in support of this being a blocker, although it has been rejected once already.
FinalBlocker +1
Can you reference the old issue, please?
I don't see it rejected: https://bugzilla.redhat.com/show_bug.cgi?id=2314875
And it was incorrect to close it as a duplicate without transferring the blocker proposal. You have to yell next time :-)
Anyway, it's very concerning that we discovered it independently just one week apart. That feels like it could affect many users. A fix is incoming, I'll test it.
Ideally I believe we should create a separate bug complaining about the error dialog not working correctly. The fix in blivet is fine, but it's just half of the problem.
Weak though, I am not 100 % for "yeah, this will stand a blocker if it was the only one on Go/No-Go".
I stumbled across this too, I kinda looked the other way because of the "Clean Windows installation" carve out.
The more I think about it though, the more I'm pretty sure the installer shouldn't just barf and die, though I can't quite find a criteria for that.
AGREED AcceptedFinalBlocker
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F41 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.