Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2274061 ** Information from BlockerBugs App:
Commented but haven't voted yet: geraldosimiao
The votes have been last counted at 2024-04-10 09:59 UTC and the last processed comment was #comment-904930
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
If Fabio's description in https://bugzilla.redhat.com/show_bug.cgi?id=2274061#c6 is accurate, then I vote:
FinalBlocker +1
especially given the "once it fails one time the failure is 'locked' forever" aspect, because that potentially means we cannot easily fix this with a post-release update.
Based on further research - https://bugzilla.redhat.com/show_bug.cgi?id=2274061#c9 - I'm changing my tentative vote to:
FinalBlocker -1
I think this is probably substantially addressed for fresh installs, and Fabio and I were still seeing it because we had got 'locked into' the bad state by launching snapshot before the 50ms wait hack was added.
Given the smaller scope,
But probibly should be a common bug for people who did prelrease installs?
We're still trying to understand the full scope of this bug, but I tested with a new user account and was able to reproduce. I think the problem actually primarily affects fresh installs, or users who have never run Snapshot before. Users who are upgrading from Fedora 39 and have run Snapshot at least once are probably fine?
On the one hand, I almost hope this would be waived under the late blocker criterion, since the bug was not reported until yesterday and we had no chance to fix it due to that.
On the other hand, due to the separate snapshot blocker bug causing crash on startup, it's probably not reasonable to expect it to have been caught any earlier. Perhaps the late blocker criterion should not apply when an app is so thoroughly broken.
We did find a ton of bugs in the portal stuff under testing today, so I'm doing a build with the portal usage disabled, and am gonna vote:
FinalFE +1
to get that build into an RC. it should avoid various kinds of weirdness caused by the portal/permissions stuff while that gets investigated upstream a bit more. we can always turn it back on with a later update.
Sure, FinalFE +1
AGREED AcceptedFinalFE
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F40 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.