Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2054473 Information from BlockerBugs App: <img alt="2054473" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2054473" />
Commented but haven't voted yet: coremodule
The votes have been last counted at 2022-02-21 16:27 UTC and the last processed comment was #comment-782619
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 certainly sad bug, but there is an easy workaround (sign in to your Google account again) and it just doesn't seem serious enough to block the release. I bet most users never use the Google account feature anyway. I agree with Chris that this wouldn't pass the final blocker test.
FinalBlocker -1 FinalFE +1 BetaFE +1
I agree that this doesn't seem to be blocking behavior, but it would be nice if we could fix it prior to release.
Same as bcotton: FinalBlocker -1 BetaFE +1
FinalBlocker -1 BetaFE +1
I agree this is kind of gross, and could probably be better presented to the user, but re-authenticating to cloud services isn't entirely unexpected.
AGREED RejectedFinalBlocker AGREED AcceptedBetaFE
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F36 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.