It's already quite long. Summary in this comment.
https://bugzilla.redhat.com/show_bug.cgi?id=1876162#c23

At this point I'm not certain about either beta FE (fix doesn't exist, could be too invasive) or final blocker. But since it's not crashing and does eventually complete an install...

BetaBlocker -1

I feel this is not such a common use case to warrant a BetaBlocker. But I'm open to discussing a FinalBlocker proposal (will add it to the bug). I'll also mark it as CommonBugs.

BetaBlocker -1

BetaBlocker -1

However, I am a bit concerned about the openSUSE remark that the package manager could produce so many snapshots easily on its own. I would be happier if snapshots were only created when a user asks for it. How will this be handled in Fedora, @chrismurphy ?

How will this be handled in Fedora, @chrismurphy ?

F33 will make no automatic snapshots

BetaBlocker -1

BetaBlocker -1

See https://bugzilla.redhat.com/show_bug.cgi?id=1876162#c26
AGREED RejectedBetaBlocker

The following votes have been closed:

• Rejected BetaBlocker (+0, 0, -4)
  • -1 by chrismurphy, kparal, lruzicka, lbrabec

Discussed during the 2020-09-08 blocker review meeting: [0]

The decision to delay the classification of this as a Final blocker bug was made as this seems like a reasonable blocker candidate but we're concerned about the extent to which it can realistically be addressed in a practical timeframe for F33. We will punt for input from installer team on this.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2020-09-08/f33-blocker-review.2020-09-08-16.00.txt

BetaFE +1

I agree with Adam's comment that it's better to get this into Beta and get more testing than to wait for final.

BetaFE +1

BetaFE +1

BetaFE +1

BetaFE +1

Changing my vote for now.

BetaFE -1

Based on comments 32 and 33 I'm now also slightly nervous. But I don't know the intent of so many 'udevadm settle' instances. Also, as described in comment 34, it's not likely to fix a more realistic case, making the fix not worth the risk.

After reading comment 34 in the bug ... if something like that should be implemented (or even decided if we want it that way), then I think we do not have enough time to make it happen in Beta.

BetaFE -1

Hmm, at the same time, if this is the fix Anaconda/blivet devs want to do, it's better to include it in Beta than Final. Perhaps the judgement call should come from them.

I'm inclined to say that we should go ahead and make the change now and see how it shakes out for Beta. If we encounter issues, we can always put them back. That's The Power of Git:tm: :wink:

BetaFE +1

AGREED AcceptedBetaFE

Discussed during the 2020-09-14 blocker review meeting: [0]

The decision to classify this bug as an "AcceptedFreezeException (Beta)" was made as it is a noticeable issue that cannot be fixed with an update.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2020-09-14/f33-blocker-review.2020-09-14-16.01.txt

The following votes have been closed:

• Accepted BetaFE (+5, 0, -2)
  • +1 by bcotton, ngompa, frantisekz, kparal, jlanda
  • -1 by chrismurphy, lruzicka

Discussed during the 2020-09-14 blocker review meeting: [0]

The decision to delay the classification of this as a blocker bug was made as we would like more evaluation from anaconda team and also testing with a real-world case (not identical snapshots) to figure out what's really plausible in an f33 timeframe before voting on this.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2020-09-14/f33-blocker-review.2020-09-14-16.01.txt

BetaFE -1

I don't believe this is a situation many users will be in. Very few operating systems use Btrfs as default, this will probably be most users' first experience with Btrfs

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

The following votes have been closed:

• Accepted BetaFreezeException (+5, 0, -2)
  • +1 by bcotton, ngompa, frantisekz, kparal, jlanda
  • -1 by chrismurphy, lruzicka