Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=1999321 Information from BlockerBugs App: <img alt="1999321" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/1999321" />
Commented but haven't voted yet: chrismurphy, lruzicka, adamwill, abbra
The votes have been last counted at 2021-09-23 12:03 UTC and the last processed comment was #comment-753348
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
BetaBlocker +1 AGREED AcceptedBetaBlocker
The following votes have been closed:
I think we should remove this blocker as it is not currently clear what exactly is causing the fault and we don't see the fault outside of Fedora infrastructure (OpenQA).
FreeIPA team does not see this as a blocker caused by anything in FreeIPA itself or its dependencies.
Agreed, as mentioned in the bug. I do think there's likely a real bug hiding here somewhere, probably something to do with cipher suites or some such, but it seems likely that it's too constrained to really need to be a Beta blocker. I have cleared the AcceptedBlocker tag on the bug. So:
REVOTE BetaBlocker
BetaBlocker 0
BetaBlocker -1
It seems to be environment-related.
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F35 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.