Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2242287 Information from BlockerBugs App: <img alt="2242287" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2242287" />
Commented but haven't voted yet: coremodule
The votes have been last counted at 2023-10-09 17:56 UTC and the last processed comment was #comment-877847
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
I'm not sure about a blocker, because this seems to be a corner case (when you have autofs directly in root). If anyone has an argument for or against, let's hear it. I'd definitely give it a FE, deadlocked systems are not fun. FinalFE +1
FinalFE +1
yeah, my read is same as @kparal , you need a fairly unusual config to trigger this, but at least:
FinalFE +1 AGREED AcceptedFinalFE
The following votes have been closed:
From what I understand currently, I don't think this is likely enough to occur to be a blocker.
FinalBlocker -1
AGREED RejectedFinalBlocker
Discussed during the 2023-10-09 blocker review meeting: [0]
The decision to classify this bug as a "RejectedBlocker (Final)" was made as the configuration to hit it seems very uncommon so it's not serious enough to block the release on.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2023-10-09/f39-blocker-review.2023-10-09-16.00.txt
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F39 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.