Description of problem: I was trying to install Fedora on a firmware RAID. After I wanted to reclaim the taken up space, Anaconda crashed. Version-Release number of selected component: anaconda-41.31 The following was filed automatically by anaconda: anaconda 41.31 exception report Traceback (most recent call first): File "/usr/lib/python3.13/site-packages/dasbus/client/handler.py", line 509, in _handle_method_error raise exception from None File "/usr/lib/python3.13/site-packages/dasbus/client/handler.py", line 483, in _get_method_reply return self._handle_method_error(error) File "/usr/lib/python3.13/site-packages/dasbus/client/handler.py", line 450, in _call_method return self._get_method_reply( File "/usr/lib64/python3.13/site-packages/pyanaconda/ui/gui/spokes/lib/resize.py", line 558, in _schedule_actions self._device_tree.RemoveDevice(obj.name) File "/usr/lib64/python3.13/site-packages/pyanaconda/ui/gui/spokes/lib/resize.py", line 571, in on_resize_clicked self._schedule_actions(obj) pyanaconda.modules.common.errors.storage.UnknownDeviceError: Volume0_0 Additional info: hawkey.log: 2024-09-12T13:48:30+0000 INFO === Started libdnf-0.73.3 === version: 41 kernel: 6.11.0-0.rc5.43.fc41.x86_64 addons: com_redhat_kdump cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-E-dvd-x86_64-41 quiet release: Fedora release 41 (Forty One) type: anaconda release_type: pre-release package: anaconda-41.31 reason: pyanaconda.modules.common.errors.storage.UnknownDeviceError: Volume0_0 product: Fedora hashmarkername: anaconda executable: /sbin/anaconda cmdline: /usr/bin/python3 /sbin/anaconda comment: I was trying to install Fedora on a firmware RAID. After I wanted to reclaim the taken up space, Anaconda crashed.
Created attachment 2046562 [details] File: lsblk_output
Created attachment 2046563 [details] File: dbus.log
Created attachment 2046564 [details] File: backtrace
Created attachment 2046565 [details] File: lorax-packages.log
Created attachment 2046566 [details] File: anaconda.log
Created attachment 2046567 [details] File: anaconda-tb
Created attachment 2046568 [details] File: lvm.log
Created attachment 2046569 [details] File: nmcli_dev_list
Created attachment 2046570 [details] File: program.log
Created attachment 2046571 [details] File: packaging.log
Created attachment 2046572 [details] File: storage.log
Created attachment 2046573 [details] File: description
Created attachment 2046574 [details] File: syslog
Created attachment 2046575 [details] File: environ
Created attachment 2046576 [details] File: os_info
Created attachment 2046577 [details] File: packaging.log
I have tried to delete the RAID array and create a new one to see whether this would have any positive effect, but on the contrary. With a fresh new array, Anaconda claims to have "no usable configuration" when attempting to do automatic partitioning. However, when using Custom partitioning, the process works normally and Fedora can be installed on that RAID.
Proposed as a Blocker for 41-final by Fedora user lruzicka using the blocker tracking app because: Violates the Firmware RAID criterion.
upstream PR: https://github.com/rhinstaller/anaconda/pull/5875 updates image for F41: https://vtrefny.fedorapeople.org/img/rhbz2311936.img
Discussed during the 2024-09-16 blocker review meeting: [1] The decision to classify this bug as a AcceptedBlocker (Final) was made: "This is accepted as a clear violation of Final criterion "The installer must be able to detect and install to firmware RAID storage devices"." [1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-09-16/f41-blocker-review.2024-09-16-16.00.log.html
FEDORA-2024-50a6d0cce2 (anaconda-41.34-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-50a6d0cce2
FEDORA-2024-50a6d0cce2 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-50a6d0cce2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-50a6d0cce2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
I downloaded the ISO that contains these changes (02915834-FEDORA-2024-50a6d0cce2-netinst-x86_64.iso) and I cannot even start Anaconda as it is crashing constantly in a VM or via PiKVM. I asked fzatlouk to test on a real bare metal in the office.
So, I have tested the above update and it still does not work as expected. Anaconda does not crash any more when attempting to reclaim the space on the RAID, however it still reports "No usable disks selected" and the installation cannot be started until I choose Custom installation and let it create the layout automatically. Then, you can install the system. I am attaching the storage.log from the affected machine.
Created attachment 2051069 [details] Storage log from the affected machine.
The original issue that this was about is resolved - one can reclaim space on Firmware RAID systems without crashing. The inability to proceed on such configuration with Automatic partitioning is split off to: https://bugzilla.redhat.com/show_bug.cgi?id=2317287
FEDORA-2024-206f8a2f56 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-206f8a2f56` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-206f8a2f56 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-206f8a2f56 (anaconda-41.35-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.