Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2317048 ** Information from BlockerBugs App:
The votes have been last counted at 2024-10-17 16:17 UTC and the last processed comment was #comment-939006
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
FinalBlocker -1 FinalFE +1
VMware isn't mentioned anywhere as release blocking and/or supported virtualization solution, it can't block Fedora.
in our release criteria about virtualization we have only covered KVM scenarios, as we can see in the release validation matrix for example: https://fedoraproject.org/wiki/Test_Results:Fedora_41_Branched_20241009.n.0_Summary#Virtualization
So, VMware its not a blocker, but really must be a FE.
OK so strictly by the rules:
I don't use VMWare myself, but if I did I'd want this a blocker. Seems this will be a show stopper for many corporate workflows.
FinalBlocker -1
We should document this, though, and ideally report it to VMware...
AGREED RejectedFinalBlocker
The following votes have been closed:
AGREED AcceptedFinalFE
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F41 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.