Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2011928 ** Information from BlockerBugs App:
Commented but haven't voted yet: adamwill, coremodule
The votes have been last counted at 2021-10-25 18:23 UTC and the last processed comment was #comment-759012
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
Booting a release-blocking deliverable seems like an important thing.
It'd be good to have someone else test and see if they can confirm, I think.
Discussed during the 2021-10-11 blocker review meeting: [0]
The decision to delay the classification of this as a blocker bug was made as this is definitely a worrying bug but so far we have only a single reporter and not much detail or feedback from kernel/arm/cloud groups. We will try to get more input on this issue this week and take further action.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-10-11/f35-blocker-review.2021-10-11-16.00.txt
AGREED AcceptedFinalFE
Discussed during the 2021-10-18 blocker review meeting: [0]
The decision to delay the classification of this bug as a blocker and accept this as an "AcceptedFreezeException (Final)" was made as, though it's very late, we're still actively researching this and can't be sure yet if it needs to block the release. Many folks are working on it actively and we hope for developments soon. We agree it's at least serious enough to grant a freeze exception in any case.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-10-18/f35-blocker-review.2021-10-18-16.00.txt
The following votes have been closed:
FinalBlocker -1 Not sure if we get anyone to test it on time.
AGREED RejectedFinalBlocker
Discussed during the 2021-10-25 blocker review meeting: [0]
The decision to classify this bug as a "RejectedBlocker (Final)" was made as we agreed on current information to reject this as a blocker and document it as an ongoing situation with vexxhost which we will try to get resolved ASAP. This is a tough call as we cannot be sure if it specific to vexxhost's environment somehow, and if the problem lies there or in Fedora 35 itself.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-10-25/f35-blocker-review.2021-10-25-16.02.txt
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.