Description of problem: Boot Fedora-Workstation-Live-x86_64-35-20210911.n.0.iso (Fedora-Server-dvd-x86_64-35-20210911.n.0.iso) on a VM which has two disks. on the BLIVET-GUI PARTITIONING page,create one software raid partition,and then try to delete it, the crash happens immediately after you click the "OK" button Version-Release number of selected component: anaconda-35.22.1 The following was filed automatically by anaconda: anaconda 35.22.1 exception report Traceback (most recent call first): File "/usr/lib/python3.10/site-packages/blivetgui/osinstall.py", line 234, in _reraise_exception raise type(exception)(message + str(exception) + "\n" + traceback) File "/usr/lib/python3.10/site-packages/blivetgui/blivetgui.py", line 569, in delete_selected_partition self._reraise_exception(result.exception, result.traceback, message, blivet.errors.DeviceFormatError: Failed to delete the device:format has not been created Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/blivetgui/blivet_utils.py", line 602, in delete_device parent.format.teardown() File "/usr/lib/python3.10/site-packages/blivet/threads.py", line 53, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.10/site-packages/blivet/formats/__init__.py", line 650, in teardown if not self._pre_teardown(**kwargs): File "/usr/lib/python3.10/site-packages/blivet/threads.py", line 53, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.10/site-packages/blivet/formats/__init__.py", line 659, in _pre_teardown raise DeviceFormatError("format has not been created") blivet.errors.DeviceFormatError: format has not been created Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-35 rd.live.check quiet executable: /sbin/anaconda hashmarkername: anaconda hawkey.log: 2021-09-17T10:44:45+0000 INFO === Started libdnf-0.63.1 === kernel: 5.14.0-60.fc35.x86_64 product: Fedora release: Fedora release 35 (Thirty Five) release_type: pre-release type: anaconda version: 35
Created attachment 1823835 [details] File: anaconda-tb
Created attachment 1823836 [details] File: anaconda.log
Created attachment 1823837 [details] File: dbus.log
Created attachment 1823838 [details] File: dnf.librepo.log
Created attachment 1823839 [details] File: environ
Created attachment 1823840 [details] File: lorax-packages.log
Created attachment 1823841 [details] File: lsblk_output
Created attachment 1823842 [details] File: nmcli_dev_list
Created attachment 1823843 [details] File: os_info
Created attachment 1823844 [details] File: program.log
Created attachment 1823845 [details] File: storage.log
Created attachment 1823846 [details] File: syslog
Created attachment 1823847 [details] File: packaging.log
upstream PR: https://github.com/storaged-project/blivet-gui/pull/294
Proposed as a Blocker for 35-beta by Fedora user lnie using the blocker tracking app because: When using both the installer-native and the blivet-gui-based custom partitioning flow, the installer must be able to: Remove a planned storage volume from the planned layout
FEDORA-2021-216be9465e has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-216be9465e
+3 in https://pagure.io/fedora-qa/blocker-review/issue/473 , marking accepted. We could potentially waive this as a late blocker, but as we have a fix and it's limited in scope, I have built an update that includes it, and will request an RC2; we can keep most RC1 tests as valid, since this change is limited to code dealing with RAID devices in blivet-gui.
Tested right now with an Fedora-KDE-Live-x86_64-35_Beta-1.1.iso without and with the new update (https://bodhi.fedoraproject.org/updates/FEDORA-2021-216be9465e). Confirmed the bug on the Beta-1.1.iso, and confirmed that the fix at the update really works fine. (I installed the rpms at a live session and then runned anaconda and tried to do the process described at this ticket).
OK, proposed fix for this will be in RC2 that is underway now.
Thanks a lot for confirming the fix, Geraldo!
FEDORA-2021-216be9465e has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-216be9465e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-216be9465e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Tested the new beta release candidate Fedora-Workstation-Live-x86_64-35_Beta-1.2.iso And the fix is already there and working fine.
Checked with Fedora-Workstation-Live-x86_64-35_Beta-1.2.iso,the bug is fixed.
Verified with Fedora-Workstation-Live-x86_64-35_Beta-1.2.iso, this bug is fixed
FEDORA-2021-216be9465e has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.