Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2006314 ** Information from BlockerBugs App:
The votes have been last counted at 2021-09-22 16:48 UTC and the last processed comment was #comment-753250
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
The justification for FinalBlocker is the same as in https://pagure.io/fedora-qa/blocker-review/issue/463#comment-752780 :
If an initial setup utility is run or intended to be run after the first boot of the installed system, then it must start successfully and each page or panel of the initial setup utility should withstand a basic functionality test. https://fedoraproject.org/wiki/Fedora_35_Final_Release_Criteria#First_boot_experience
FinalBlocker +1
As for the BetaBlocker, I'm not sure. We don't have an explicit networking criterion. The fact that you need to remove the connection first and create it again is pretty bad, but at the same time it might be acceptable for Beta (if documented as CommonBugs).
BetaBlocker 0 BetaFE +1
FinalBlocker +1 BetaFE +1 BetaBlocker 0
Same reasoning as Kamil
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.