Cannot parse given Error object I was trying to set up a RAID 0 device when this happened. I will provide more information later. ---[ Frontend Stacktrace ]--- this.parseV8OrIE (http://127.0.0.1/cockpit/@localhost/node_modules/error-stack-parser/error-stack-parser.js:35:22) Promise(function (http://127.0.0.1/cockpit/@localhost/node_modules/stacktrace-js/stacktrace.js:106:61) Promise(function (http://127.0.0.1/cockpit/@localhost/node_modules/stacktrace-js/stacktrace.js:105:19) componentDidMount (http://127.0.0.1/cockpit/@localhost/src/components/Error.jsx:812:53) onunhandledrejection (http://127.0.0.1/cockpit/@localhost/src/components/Error.jsx:821:62) ---[ System & Environment Information ]--- OS: Fedora Linux 44 (Workstation Edition Prerelease) Anaconda version: 44.21 Anaconda UI version: 66.1.g8b67635c
Created attachment 2131850 [details] Log file: /tmp/journal.log
Created attachment 2131851 [details] Log file: /tmp/anaconda.log
Created attachment 2131852 [details] Log file: /tmp/storage.log
Created attachment 2131853 [details] Log file: /tmp/program.log
Created attachment 2131854 [details] Log file: /tmp/packaging.log
Created attachment 2131855 [details] Log file: /tmp/anaconda-webui.log
Proposed as a Blocker for 44-beta by Fedora user lruzicka using the blocker tracking app because: I am proposing this as a beta blocker based on the following criterion: https://fedoraproject.org/wiki/Fedora_44_Beta_Release_Criteria#Custom_partitioning
Summary: Anaconda WebUI crashes when creating RAID 0 on GPT-initialized virtio disks during installation Description: While attempting to configure a RAID 0 array in the Anaconda WebUI during Fedora 44 installation, the installer crashed immediately after attempting to create the RAID device. Version: Fedora 44 Beta (Release Candidate 1.2) Environment: Installation method: Anaconda WebUI Architecture: x86_64 (virtual machine) Virtualization: VM with virtio disks Storage configuration: vda – 20 GB (virtio) vdb – 20 GB (virtio) vdc – 10 GB (virtio) Steps to Reproduce: 1. Boot Fedora 44 Beta (RC 1.2) installer in a virtual machine. 2. Attach three virtio disks: 20 GB (vda) 20 GB (vdb) 10 GB (vdc) 3. In Anaconda WebUI storage configuration: a) On vdc (10 GB disk), create: EFI System Partition and /boot partition b) On vda and vdb (20 GB disks): Initialize both disks with GPT partition tables. c) Attempt to create a RAID 0 array using space on vda and vdb. d) Confirm the RAID creation. Expected Result: RAID 0 device should be created successfully and available for further partitioning or filesystem configuration or an error message should be shown that the operation is not legal. Actual Result: Anaconda WebUI crashes immediately after attempting to create the RAID device. The installer reports an internal error and terminates the storage configuration workflow. Reproducibility: Occurred during initial attempt (frequency not yet tested multiple times). Additional Information: See the crash report generated by Anaconda for details
I tried to follow the reproducer to the letter, but saw no anaconda crash. On RAID0 I created the / partition, installed the system, and it boots fine. Lukas, can you reproduce it again? This might be perhaps related to the previous contents present on the disk.
Something throws an error but it's not properly formatted. And when ErrorRenderer tries to parse, the parser it uses, so the error-stack-parser blows up. I can't see in the logs what the error was, but I can make sure that Error handling does not crash the installer, if the exception is not in expected format.
The real error was covered up by an exception in the error reporting dialog itself: I have a fix for that https://github.com/rhinstaller/anaconda-webui/pull/1198 The real error is hidden in the journal: Mar 03 10:06:46 localhost-live org.fedoraproject.Anaconda.Modules.Storage[3529]: WARNING:dasbus.server.handler:The call org.fedoraproject.Anaconda.Modules.Storage.DeviceTree.Viewer.GetDiskTotalSpace has failed with an exception: Mar 03 10:06:46 localhost-live org.fedoraproject.Anaconda.Modules.Storage[3529]: Traceback (most recent call last): Mar 03 10:06:46 localhost-live org.fedoraproject.Anaconda.Modules.Storage[3529]: File "/usr/lib/python3.14/site-packages/dasbus/server/handler.py", line 455, in _method_callback Mar 03 10:06:46 localhost-live org.fedoraproject.Anaconda.Modules.Storage[3529]: result = self._handle_call( Mar 03 10:06:46 localhost-live org.fedoraproject.Anaconda.Modules.Storage[3529]: interface_name, Mar 03 10:06:46 localhost-live org.fedoraproject.Anaconda.Modules.Storage[3529]: ...<2 lines>... Mar 03 10:06:46 localhost-live org.fedoraproject.Anaconda.Modules.Storage[3529]: **additional_args Mar 03 10:06:46 localhost-live org.fedoraproject.Anaconda.Modules.Storage[3529]: ) Mar 03 10:06:46 localhost-live org.fedoraproject.Anaconda.Modules.Storage[3529]: File "/usr/lib/python3.14/site-packages/dasbus/server/handler.py", line 265, in _handle_call Mar 03 10:06:46 localhost-live org.fedoraproject.Anaconda.Modules.Storage[3529]: return handler(*parameters, **additional_args) Mar 03 10:06:46 localhost-live org.fedoraproject.Anaconda.Modules.Storage[3529]: File "/usr/lib64/python3.14/site-packages/pyanaconda/modules/storage/devicetree/viewer_interface.py", line 202, in GetDiskTotalSpace Mar 03 10:06:46 localhost-live org.fedoraproject.Anaconda.Modules.Storage[3529]: return self.implementation.get_disk_total_space(disk_ids) Mar 03 10:06:46 localhost-live org.fedoraproject.Anaconda.Modules.Storage[3529]: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^ Mar 03 10:06:46 localhost-live org.fedoraproject.Anaconda.Modules.Storage[3529]: File "/usr/lib64/python3.14/site-packages/pyanaconda/modules/storage/devicetree/viewer.py", line 508, in get_disk_total_space Mar 03 10:06:46 localhost-live org.fedoraproject.Anaconda.Modules.Storage[3529]: disks = self._get_devices(disk_ids) Mar 03 10:06:46 localhost-live org.fedoraproject.Anaconda.Modules.Storage[3529]: File "/usr/lib64/python3.14/site-packages/pyanaconda/modules/storage/devicetree/viewer.py", line 295, in _get_devices Mar 03 10:06:46 localhost-live org.fedoraproject.Anaconda.Modules.Storage[3529]: return list(map(self._get_device, device_ids)) Mar 03 10:06:46 localhost-live org.fedoraproject.Anaconda.Modules.Storage[3529]: File "/usr/lib64/python3.14/site-packages/pyanaconda/modules/storage/devicetree/viewer.py", line 285, in _get_device Mar 03 10:06:46 localhost-live org.fedoraproject.Anaconda.Modules.Storage[3529]: raise UnknownDeviceError(device_id) Mar 03 10:06:46 localhost-live org.fedoraproject.Anaconda.Modules.Storage[3529]: pyanaconda.modules.common.errors.storage.UnknownDeviceError: MDRAID-localhost-live:raid0
I tried hard today, but I could not reproduce this any more. The original error might have been a race condition and because I could not hit it today, I am not hitting the second error either. Thank you for fixing this, Katerina.
Proposed as a Freeze Exception for 44-beta by Fedora user kkoukiou using the blocker tracking app because: Some backend exceptions where incorrectly parsed causing a random crash which was covering up the real exception. The fix was thoroughly tested and will make exceptions make sense.
FEDORA-2026-db45346513 (anaconda-webui-67-1.fc45) has been submitted as an update to Fedora 45. https://bodhi.fedoraproject.org/updates/FEDORA-2026-db45346513
Let's close this when it's fixed in Fedora 44, not Rawhide.
FEDORA-2026-f5c7f9e4c2 (anaconda-webui-67-2.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-f5c7f9e4c2
FEDORA-2026-db45346513 (anaconda-webui-67-1.fc45) has been pushed to the Fedora 45 stable repository. If problem still persists, please make note of it in this bug report.
I reproduced this and tested the fix by introducing a fake failure in a backend call. I was not able to create a reproducer without patching WebUI or Anaconda code to create a backend crash.
FEDORA-2026-f5c7f9e4c2 has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-f5c7f9e4c2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-f5c7f9e4c2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
During Beta Go/NoGo meeting [1]: !agreed 2444078 - RejectedBlocker (Beta) - this is rejected. The underlying RAID bug is rejected as it doesn't seem to be reproducible. The 'anaconda shows the wrong error' bug is rejected as we can determine the correct error from the logs if necessary, and it's definitely not affecting all failures, only ones which break the traceback parser [1] https://meetbot-raw.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-03-05/
FEDORA-2026-f5c7f9e4c2 (anaconda-webui-67-2.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.