FinalBlocker +1

Discussed during the 2023-09-25 blocker review meeting: [0]

The decision to delay the classification of this as a blocker bug was made as ,per @kparal, it seems this might be a timing issue and it would be good for other folks to test and see if they're affected and if so, how often (and maybe get some feedback from the devs). We will punt for at least a week.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2023-09-25/f39-blocker-review.2023-09-25-16.02.txt

Based on the communication in the Bugzilla, I tend to be

FinalBlocker -1
CommongBugs +1

Feels a little too intermittent to be block on.

FinalBlocker -1
CommonBugs +1

FinalBlocker -1

I played with this today, and it really happens quite often. On a typical vda1(biosboot)+vda2(boot,ext4)+vda3(root,btrfs) Fedora disk layout, I hit this very frequently on vda2. It's a race condition, but I'd say between 20-50% for me. And it is really scary when it seems like the installer, which you just configured (or even used already) to format some of your partitions suddenly seems to freeze. Many people will not realize that keyboard controls work, it really seems frozen. It might happen when you've already performed some changes (erased some partitions) and now you're working on a second pass. Then the installer "freezes" and you do what - hard reboot?

Also, I tested this with F38 and F37 and couldn't replicate it. This is a new problem.

FinalBlocker +1

Thanks,adorable but professional Kamil.
For those who think this should Not be considered as a blocker,due to it's Not happens highly frequently:1)I just tried another three times on my work laptop, I try to format vda2, I succeed once,but it stucks again when I try to format vda1,so again,100% reproducible.I think it's pretty safe to say that it's much more easy to hit on this bug on bare metal than on VM2)users will use formatting disk option more likely during bare metal installation than on VM3)formatting stuck is only one symptom,another is the mount point pop-up gets stuck,so during one VM installation,user may luckily enough to escape the formatting stuck,but they may not luck enough to escape the mount-point stuck:(
At least,I think we should not reject this as a blocker until someone could disprove my conclusion: this happens 100%(or,at least highly frequently) on bare metal installation,or wait until I come back from my vacation(5 days later) to do more testing on my two test bare metal machines to disprove it by myself.

Also, I tested this with F38 and F37 and couldn't replicate it. This is a new problem.
I tested on F38 VM, couldn't reproduce in my 5 tries,forgot to mention it in my last bug comment,thank adorable Kamil,again^^

FinalBlocker +1

AGREED AcceptedFinalFreezeException

Discussed during the 2023-10-02 blocker review meeting: [1]

Agreed punt blocker (delay decision) AcceptedFreezeException (Final) - This does appear bad, but we can't reach a consensus. We're going to punt for now and perhaps have more testing done in the meantime. We do grant it FE status.

[1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2023-10-02/f39-blocker-review.2023-10-02-16.01.log.txt

The following votes have been closed:

• Accepted FinalFreezeException (+0, 0, -0)

The issue is borderline. I'm going to cast my useless vote so I know I looked at it.

FinalBlocker 0

FinalBlocker -1

As in the meeting

Based on both the bug and my own testing I've gotta be:

FinalBlocker +1

yes the workaround is easy, but only if you think of it or look it up. If you don't, you just feel like the thing is hung. And it really does happen pretty often. It seems pretty bad to me.

I understand your concerns and I want to support you, who'd like to block on this, so I am revoting, although I think that 20-50% on a certain setup will be far less in reality with all other possible setups.

FinalBlocker +1

If I understand it correctly, this is not about a certain setup, if affects everybody. There might be differences whether a first or second or third partition triggers this, but hardware-wise this seems to occur everywhere.

yeah, from my reading of the bug, everyone who's actually tried to reproduce this has been able to. it seems to happen a bit more for some folks and a bit less for others, but not really a huge difference.

FinalBlocker +1

That gives a total of +6 / -3, so:

AGREED AcceptedFinalBlocker

The following votes have been closed:

• Accepted FinalBlocker (+6, 1, -3)
  • +1 by imsedgar, lruzicka, kparal, lnie, adamwill, asciiwolf
  • 0 by zbyszek
  • -1 by nielsenb, geraldosimiao, frantisekz

Release F39 is no longer tracked by BlockerBugs, closing this ticket.