Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2123494 Information from BlockerBugs App: <img alt="2123494" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2123494" />
The votes have been last counted at 2022-09-02 17:01 UTC and the last processed comment was #comment-814973
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
It must be possible to join the system to a FreeIPA or Active Directory domain at install time and post-install, and the system must respect the identity, authentication and access control configuration provided by the domain.
(Edit to cite the appropriate basic criterion and not the text to my kid's teacher about their missing iPad)
It is possible to do that. You can do it via realmd, you can do it via cockpit, you can do it via kickstart. You just can't do it via g-i-s, which isn't a very commonly-used way I don't think, and we haven't tested it for years.
BetaBlocker -1
The relevant criterion for me is Final "If an initial setup utility is run or intended to be run after the first boot of the installed system, then it must start successfully and each page or panel of the initial setup utility should withstand a basic functionality test". Even then it's a bit borderline; do we consider this "basic" functionality of the account page?
I would say:
BetaFE +1
though, as obviously can't be fixed with an update.
BetaBlocker -1 BetaFE +1
I think that this is bad enough to break the Basic Functionality criterion and therefore I suggest to make it a Final Blocker instead. In Beta, users can choose a different method, but we should not ship something like that for Final.
BetaFE +1 BetaBlocker -1 FinalBlocker +1
I agree that we shouldn't ship with such a basic error in user interface. If AdamW doesn't want this to block beta, that's fair, but let's block final.
I'll keep my BetaBlocker vote unchanged, but won't lobby for it.
BetaFE +1 FinalBlocker +1
AGREED AcceptedBetaFE RejectedBetaBlocker AcceptedFinalBlocker
The following votes have been closed:
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.