Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=1872068
Commented but haven't voted yet: coremodule
The votes have been last counted at 2020-08-31 16:58 UTC and the last processed comment was #comment-674631
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review
After reading through: https://bugzilla.redhat.com/show_bug.cgi?id=1872068 https://bugzilla.redhat.com/show_bug.cgi?id=1871986 https://bugzilla.redhat.com/show_bug.cgi?id=1867930 (uncertain if this is linked) this is certainly concerning. It happened to several people using different packages. I couldn't replicate the issue. I guess we'll need to wait a bit and try to untangle the issue a bit, so that we can have at least a basic guess of how many people might be affected and in which situations.
BetaFE +1 BetaBlocker -1
It's not universally reproducible and doesn't appear to affect a "default" setup, so it's hard to call it a blocker. But it's definitely worth fixing prior to release.
BetaFE +1
Discussed during the 2020-08-31 blocker review meeting: [0]
AGREED RejectedBetaBlocker AcceptedBetaFE This is rejected on the grounds it's not reproducible from a clean install/upgrade scenario, which is what the criteria cover. Accepted as an FE as this is a serious bug for folks who happen to be in whatever state triggers it (we're not sure yet).
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2020-08-31/f33-blocker-review.2020-08-31-16.00.txt
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F33 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.