Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2117859 Information from BlockerBugs App: <img alt="2117859" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2117859" />
Commented but haven't voted yet: adamwill, coremodule
The votes have been last counted at 2022-08-22 21:22 UTC and the last processed comment was #comment-812525
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 per Adam's justification about dramatically reducing test coverage, if nothing else
So, turns out disabling dnssec validation on the server avoids this problem. That makes the evaluation a bit trickier, I guess, because we could argue that's a sufficiently okay workaround for Beta.
I think at that point the key is whether this affects upgrades of existing servers with dnssec validation enabled, because if it does, that's likely a violation of "It must be possible to successfully complete a direct upgrade from a fully updated installation of each of the last two stable Fedora Server releases with the system configured as a FreeIPA domain controller or postgresql server as specified in the relevant criteria. The upgraded system must meet all relevant release criteria, including criteria relating to functionality of the server software."
Unfortunately, we've had dnssec turned off on the upgrade tests for years because of https://bugzilla.redhat.com/show_bug.cgi?id=1999321 . I guess I can try turning it back on again and see what happens.
Discussed during the 2022-08-22 blocker review meeting: [0]
The decision to delay the classification of this as a blocker bug was made so adamw can do some more research and get the story of what exactly is affected and what needs doing sorted out.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-08-22/f37-blocker-review.2022-08-22-16.01.txt
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.