Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2103835 ** Information from BlockerBugs App:
Commented but haven't voted yet: coremodule
The votes have been last counted at 2022-08-22 21:23 UTC and the last processed comment was #comment-812527
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
This seems to violate: https://fedoraproject.org/wiki/Fedora_37_Beta_Release_Criteria#Virtualization_requirements Specifically, virt-install is part of the virt-manager stack, which is supported and release blocking, and the linked documentation even recommends virt-install for installation at the very top.
virt-install
Given that this only affects virt-install but not virt-manager itself, I think it would be OK to make it block just Final. But because this change also prevents test automation from running (Lili speaks about fedora-release-autotest for virtualization, Martin Pitt in the PR mentioned Anaconda testing), I think keeping this a Beta blocker is better.
This bug limits the test coverage, so we should fix it as soon as possible in the process.
Betablocker +1
AGREED AcceptedBetaBlocker
Discussed during the 2022-08-22 blocker review meeting: [0]
The decision to classify this bug as an "AcceptedBlocker (Beta)" was made as a violation of the virtualization criteria per kparal's comment on the ticket. We also note its impact on important test systems (anaconda CI and fedora-release-autotest).
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-08-22/f37-blocker-review.2022-08-22-16.01.txt
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.
Log in to comment on this ticket.