Bug 2351830

Created attachment 2079997 [details]
webui.log

Created attachment 2079998 [details]
storage.log

Created attachment 2079999 [details]
journal

Created attachment 2080000 [details]
anaconda.log

Please add the steps for the reproducer.

Sorry for the a bit late reply, I was trying to find more blocker like bugs before the go/not-go meeting.
Here is reproducer:
1.boot Fedora-Workstation-Live-42_Beta-1.4.x86_64.iso on a VM with 3 disks
2.select all the disks, and launch storage editor
3 create a mdraid device( I selected raid1) on top of two disks, then delete it,and you will see this crash immediately after you click"return to installation"(100% reproduciable)

Please note:
1.on step3,after you delete the mdraid device, you will see this bug even if you format the disk ,but you will Not see this bug if you create partition table on the disk
2.If you click quit and restart anaconda without rebooting the system,you will not see this bug anymore,and you will see it again after you reboot the machine.
3.If you boot a system with an existing raid device on step1,you don't need to create another one on step3.

I also checked with mdraid on top of partitions, it is Not affected by this bug.

 Still see this crash with anaconda-webui-27-1.fc42.noarch, 100%(3/3) reproducible on deleting an existing on top of disks raid device.
 Gonna to propose it as a final blocker to broadcast this bug, and draw more attention.

Proposed as a Blocker for 42-final by Fedora user lnie using the blocker tracking app because:

 Violates  "Remove existing storage volumes" part of https://fedoraproject.org/wiki/Fedora_42_Beta_Release_Criteria#Custom_partitioning

Upstream PR: https://github.com/rhinstaller/anaconda-webui/pull/713

Created attachment 2081097 [details]
updates.img with fix for pre-verification while PR is open

*** Bug 2353153 has been marked as a duplicate of this bug. ***

Just a note, I discovered the same issue in bug 2353153 (with perhaps a bit different steps).

+6 in https://pagure.io/fedora-qa/blocker-review/issue/1802 , marking accepted.

FEDORA-2025-63711d039a (anaconda-42.27.7-1.fc42 and anaconda-webui-29-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-63711d039a

FEDORA-2025-63711d039a has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-63711d039a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-63711d039a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

With these two updates:
https://bodhi.fedoraproject.org/updates/FEDORA-2025-63711d039a
https://bodhi.fedoraproject.org/updates/FEDORA-2025-f696bd8401
I tried to reproduce the bug and it no longer crashes. I think it's fixed.

FEDORA-2025-63711d039a has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-63711d039a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-63711d039a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2025-63711d039a (anaconda-42.27.9-1.fc42 and anaconda-webui-30-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.