Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2015508 ** Information from BlockerBugs App:
The votes have been last counted at 2021-10-19 15:15 UTC and the last processed comment was #comment-758324
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
Hmmm. It's bad, yes, but this might be enough of an edge case that it's not important enough to block release? Feels too much like a QE testcase rather than normal user behavior. Some users are undoubtedly going to hit this, but probably not very many.
And it's not clear whether this is a regression. I wouldn't be surprised if this has been around for a while and we just never noticed.
-1 FinalBlocker +1 FinalFE
Feels too much like a QE testcase rather than normal user behavior.
This is normal user behaviour, if the user is @kparal. I agree that this might not hit lots of users though. Nice thing would be to inform in CommonBugs if this does not get fixed in time.
FinalBlocker -1 FinalFE +1
Yeah, same. It's a pretty odd scenario, and worst case if you hit it, just reinstall, or use some kinda rescue setup (rescue boot, live image, systemd debug shell...) to set a root password. It's a bug, but not a blocker.
AGREED RejectedFinalBlocker AGREED AcceptedFinalFE
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.