-1 FinalBlocker

It's a "soft" -1. I looked at the screencast[1], deleting an existing Btrfs is not possible, so you can't create other file-systems. I learn[2] this is a missing feature in Cockpit Storage. Given the targeted F42 GA is under a month, I'm not sure there is enough time to get this unblocked.

There seems to be a workaround[3] — deleting the Btrfs sub-volume allows you to delete the full device. Isn't this enough to make it a no-blocker for Final?

[1] https://bugzilla-attachments.redhat.com/attachment.cgi?id=2080065
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2352385#c11
[3] https://bugzilla.redhat.com/show_bug.cgi?id=2352385#c7

"deleting the Btrfs sub-volume allows you to delete the full device." yeah, it seems this is how btrfs works indeed, one can't delete a volume if it has subvolumes in it, or even snapshots (that are in fact subvolumes theirselves.

I'm also a very "soft" -1 on this. Lawyering the cited custom partitioning criteria a bit, it doesn't explicitly say anything about multi-disk non-RAID arrangements or BTRFS subvolumes.

FinalBlocker -1

FinalBlocker -1

FinalBlocker -1

Discussed during the 2025-03-17 blocker review meeting [1]:

• AGREED: 2352385 - AcceptedFreezeException (Final) - this is accepted as an FE as it's a desirable feature that it would be good to get into F42 if we can land it in enough time to test it. we won't take it very late during freeze

[1] https://meetbot-raw.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2025-03-17/f42-blocker-review.2025-03-17-16.00.log.html

AGREED RejectedFinalBlocker AcceptedFinalFE

The following votes have been closed:

• Rejected FinalBlocker (+0, 0, -4)
  • -1 by kashyapc, nielsenb, derekenz, geraldosimiao
• Accepted FinalFreezeException (+0, 0, -0)

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