Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=1950258 ** Information from BlockerBugs App:
Commented but haven't voted yet: adamwill, coremodule
The votes have been last counted at 2021-04-19 19:01 UTC and the last processed comment was #comment-728283
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
I don't think the cited criterion quite applies directly, but when coupled with the Beta criterion:
The release must be able host virtual guest instances of the same release.
I think that gets us there.
FinalBlocker -1
I agree with Ben that this criterion applies only to the bare-metal installation of Fedora, not this scenario. I managed to attach a pendrive to a gest VM on my f34 host, only problem is that it work right from the start, but when removed and reinserted guest machine doesn't recognize the pendrive a second time. I don't see how this contradicts the criterion "the release must be able host virtual..."
the criterion is really meant to be for bare metal, yeah. I don't think we envisaged it being stretched to VM bugs in this way. I'm not sure it really "feels" like a release blocker to me, either...
reasonable. FinalBlocker -1
Perhaps a FinalFE instead?
@geraldosimiao Is there a workaround available?
AGREED RejectedFinalBlocker
Discussed during the 2021-04-19 blocker review meeting: [0]
The decision to classify this bug as a "RejectedBlocker (Final)" was made as we agree that this does not really violate the criteria as they stand.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-04-19/f34-blocker-review.2021-04-19-16.00.txt
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F34 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.