Violating the custom partitioning criterion, so

FinalBlocker +1

FinalBlocker +1

FinalBlocker +1

My investigation:
https://bugzilla.redhat.com/show_bug.cgi?id=2455855#c6

Violates Beta “Custom partitioning” criterion: installer must reject invalid configurations without crashing.

Anaconda never crashes, and the configuration is rejected. Unfortunately no further steps are possible.

At this point I think we don't have a criterion that would target this problem. It's also not a huge issue, there are a number of if's - the user must mount the filesystems even though it's not required/desired (sure, many people don't know, and the UI isn't clear about this), and the user must mount if in the wrong order. And even if that all happens, you still get a decent error message - you just can't fix the situation (outside of rebooting or unmounting manually). It's not terrible.

For the moment:
FinalBlocker 0

But I guess I see it closer to FB -1, this can be documented.

Of course:
FinalFE +1

After the user has mounted the btrfs subvolumes in the wrong order:
- the storage editor rejects a valid storage configuration. This does not violate "Reject or disallow invalid disk and volume configurations without crashing".
- it is not possible to delete the newly created btrfs partition. This violates "Remove a planned storage volume from the planned layout" .
- it is not possible to delete an existing btrfs partition. This violates "Remove existing storage volumes".

Feels like a violation of the "Broadly what it's 'meant to mean' is that you should be able to do anything sane that the Installation Destination spoke attempts to let you do, without the installer exploding or failing." part of the disk layouts criteria.

FinalBlocker +1
FinalFE +1

AGREED RejectedFinalBlocker AcceptedFinalFreezeException

Discussed at the 2026-04-13 (blocker / freeze exception) review meeting:

This is an awkward corner case if you encounter it, but you have to do something that's not really necessary to hit it (try and mount filesystems). It doesn't crash the installer or eat any data; you just get a bit stuck. You can recover with a manual unmount, or by rebooting and trying again. We agreed this doesn't really clearly violate either the cited criterion or the Final "Disk layouts" criterion. It's accepted as an FE because we would like to fix this small footgun safely if possible.

https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/2026-04-13/f44-blocker-review.2026-04-13-16.00.log.txt

The following votes have been closed:

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

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