that is a thought one, it does create and exclude the partitions, it works if you start over again as showed by Kamil, and it don't crash as said by the criterion "Reject or disallow invalid disk and volume configurations without crashing." but it does not work as one might expect. I'm prone for a "common bugs" issue, but, as it does not work as one might expect after re-creating MDRAID inside the same workflow I'll vote for a FB (but prone to change it do FE)

FinalBlocker +1

I'd personally say this fails the "Remove a planned storage volume from the planned layout" criteria so for this I am.

FinalBlocker +1

FinalBlocker +1

I can see this either way. This one doesn't seem super likely to cause unintended data loss, and is work-around-able. In that regard it doesn't necessarily pass "the last blocker" test for me.

But the cited criteria does specifically call out "Remove a planned storage volume from the planned layout" as well as software RAID.

FinalBlocker +1

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

• AGREED: 2354798 - AcceptedBlocker (Final) - this is accepted as a violation of Beta custom partition criterion "...the installer must be able to: Correctly interpret, and modify as described below ... software RAID arrays at RAID levels 0, 1 and 5 containing ext4 partitions ... Remove existing storage volumes ... Create mount points backed by ext4 partitions, LVM volumes or btrfs volumes, or software RAID arrays at RAID levels 0, 1 and 5 containing ext4 partitions"

[1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2025-03-31/f42-blocker-review.2025-03-31-16.01.log.html

AGREED AcceptedFinalBlocker

The following votes have been closed:

• Accepted FinalBlocker (+4, 0, -0)
  • +1 by geraldosimiao, boniboyblue, derekenz, nielsenb

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