Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2115865 Information from BlockerBugs App: <img alt="2115865" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2115865" />
Commented but haven't voted yet: adamwill, coremodule
The votes have been last counted at 2022-08-31 16:58 UTC and the last processed comment was #comment-814554
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
Come Go/No-Go, I'd be open to waiving this based on the "moderate workaround" part of the criterion, but we're not there yet, so I'd rather proceed with this as a blocker for now.
My understanding of IPA isn't great, but I'm assuming we're calling this a blocker under the FreeIPA Server Requirements criterion?
I'm gonna leave this for the meeting so I can explain the exact state in more detail.
AGREED RejectedBetaBlocker AGREED AcceptedBetaFE
Discussed during the 2022-08-29 blocker review meeting: [0]
The decision to classify this bug as a "RejectedBlocker (Beta)" and an "AcceptedFreezeException (Beta)" was made on the grounds that dnssec functionality is not covered in the criteria, and the bug does not affect default functionality. It's accepted as a freeze exception because we do consider dnssec support important and would like this fixed if we can also fix 2117859 so things work correctly.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-08-29/f37-blocker-review.2022-08-29-16.01.txt
The following votes have been closed:
FinalBlocker +1
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F37 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.