Installation of the system failed: Storing configuration files and kickstarts org.fedoraproject.Anaconda.Error: 'NoneType' object has no attribute 'path' ---[ System & Environment Information ]--- OS: Fedora Linux 44 (Workstation Edition) Anaconda version: 44.30 Anaconda UI version: 68
Created attachment 2137268 [details] Log file: /tmp/journal.log
Created attachment 2137269 [details] Log file: /tmp/anaconda.log
Created attachment 2137270 [details] Log file: /tmp/storage.log
Created attachment 2137271 [details] Log file: /tmp/program.log
Created attachment 2137272 [details] Log file: /tmp/packaging.log
Created attachment 2137273 [details] Log file: /tmp/anaconda-webui.log
## Root Cause Analysis I've analyzed the attached logs and identified the root cause of this installation failure. **The Problem:** The installation fails during kickstart generation with `AttributeError: 'NoneType' object has no attribute 'path'` at line 84 of `/usr/lib64/python3.14/site-packages/pyanaconda/modules/storage/partitioning/manual/manual_module.py`. **What Happened:** From storage.log analysis: 1. **Initial Detection** (line 5820-5855): Anaconda discovered an existing BTRFS volume with UUID `8896fac0-a1a2-4054-8acb-3535fbfb54a8` (device ID 396) on the MD RAID array 2. **Mount Point Request** (line 6188-6209): A mount point request was created referencing this device: ``` MountPointRequest(device_spec='BTRFS-8896fac0-a1a2-4054-8acb-3535fbfb54a8', ..., reformat=True) ``` 3. **Device Replacement** (line 6652-6669): When `reformat=True` was processed, Anaconda created a **new** BTRFS device (ID 475) with a **different** UUID: `72baea7d-eb50-4a01-8b67-6255dc38316e` 4. **Kickstart Generation Failure** (line 7524-7525): When generating the kickstart file, the code tries to lookup the device by the **original** UUID (`8896fac0-a1a2-4054-8acb-3535fbfb54a8`): ``` DEBUG:blivet: DeviceTree.get_device_by_device_id: device_id: BTRFS-8896fac0-a1a2-4054-8acb-3535fbfb54a8 DEBUG:blivet: DeviceTree.get_device_by_device_id returned None ``` The lookup returns `None` because that device no longer exists—it was replaced by device 475 with the new UUID. 5. **Crash** (line 7549): The code attempts `mount_data.device = device.path` without checking if `device` is `None`, causing the AttributeError. **Stack Trace:** ``` File "...pyanaconda/modules/storage/partitioning/manual/manual_module.py", line 84, in setup_kickstart mount_data.device = device.path AttributeError: 'NoneType' object has no attribute 'path' ``` **Reproduction Scenario:** This bug occurs when using manual partitioning with: - BTRFS filesystem on an MD RAID array - Reformatting an existing BTRFS volume (`reformat=True`) - The mount point request retains the old device UUID instead of updating to the new device created during reformatting **Suggested Fix:** The code in `manual_module.py:84` needs either: 1. Null-checking before accessing `device.path`, OR 2. Properly updating mount point requests to reference the new device UUID when a device is reformatted **Impact:** Installation-blocking bug that prevents completing Fedora 44 installations when reformatting BTRFS volumes on MD RAID arrays.
Proposed as a Blocker for 44-final by Fedora user lruzicka using the blocker tracking app because: https://fedoraproject.org/wiki/Fedora_44_Beta_Release_Criteria#Custom_partitioning
I do have an 'old' unmerged fix for this: https://github.com/rhinstaller/anaconda/pull/6767
On a repeated run, this did not happen any more and the installation completed fine, so it probably only occurs occasionally. I am keeping the blocker status just for the sake of the discussion.
I was never able to reporduce it, therefore I had incorrectly considered it fixed in F44. However, I realized has been reported by more users for F44 (>10 bug reports). https://bugzilla.redhat.com/buglist.cgi?quicksearch=component%3Danaconda%20version%3D44%20NoneType&list_id=13666187 Since we have the fix ready, if the release skips by a week, please grant this a FE status if not a blocker.
Katerina, are *all* the 'NoneType' object has no attribute 'path' bugs likely the same as this? There do seem to be a lot: https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&classification=Fedora&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cshort_desc%2Cchangeddate%2Cbug_severity&component=anaconda&list_id=13666248&order=id%2C%20&product=Fedora&query_format=advanced&short_desc=%27NoneType%27%20object%20has%20no%20attribute%20%27path%27&short_desc_type=substring
Discussed at 2026-04-16 Go/No-Go meeting, acting as a blocker review meeting: https://meetbot-raw.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-04-16/f44-final-go-no-go-meeting.2026-04-16-18.00.html . Accepted as a blocker as a violation of various storage criteria in the case you are unlucky enough to hit this bug; we do believe the 31 bugs listed in the search above, plus others closed as dupes, are likely all (or almost all) this bug, and that seemed like enough reports to count it as a blocker. Katerina, please do a build with the fix ASAP, thanks!
FEDORA-2026-de98ec2a35 (anaconda-44.30-2.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-de98ec2a35
FEDORA-2026-de98ec2a35 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-de98ec2a35` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-de98ec2a35 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
*** Bug 2438995 has been marked as a duplicate of this bug. ***
*** Bug 2445392 has been marked as a duplicate of this bug. ***
*** Bug 2445486 has been marked as a duplicate of this bug. ***
*** Bug 2446431 has been marked as a duplicate of this bug. ***
*** Bug 2446971 has been marked as a duplicate of this bug. ***
*** Bug 2446890 has been marked as a duplicate of this bug. ***
*** Bug 2446972 has been marked as a duplicate of this bug. ***
*** Bug 2446973 has been marked as a duplicate of this bug. ***
*** Bug 2446974 has been marked as a duplicate of this bug. ***
*** Bug 2447221 has been marked as a duplicate of this bug. ***
*** Bug 2448356 has been marked as a duplicate of this bug. ***
*** Bug 2448357 has been marked as a duplicate of this bug. ***
*** Bug 2449463 has been marked as a duplicate of this bug. ***
*** Bug 2450184 has been marked as a duplicate of this bug. ***
*** Bug 2450375 has been marked as a duplicate of this bug. ***
*** Bug 2450430 has been marked as a duplicate of this bug. ***
*** Bug 2452770 has been marked as a duplicate of this bug. ***
*** Bug 2452856 has been marked as a duplicate of this bug. ***
*** Bug 2452857 has been marked as a duplicate of this bug. ***
*** Bug 2457287 has been marked as a duplicate of this bug. ***
*** Bug 2454386 has been marked as a duplicate of this bug. ***
*** Bug 2452919 has been marked as a duplicate of this bug. ***
*** Bug 2447701 has been marked as a duplicate of this bug. ***
*** Bug 2459527 has been marked as a duplicate of this bug. ***
*** Bug 2458429 has been marked as a duplicate of this bug. ***
*** Bug 2455131 has been marked as a duplicate of this bug. ***
*** Bug 2452862 has been marked as a duplicate of this bug. ***
*** Bug 2447555 has been marked as a duplicate of this bug. ***
*** Bug 2445989 has been marked as a duplicate of this bug. ***
*** Bug 2445777 has been marked as a duplicate of this bug. ***
*** Bug 2458844 has been marked as a duplicate of this bug. ***
FEDORA-2026-de98ec2a35 (anaconda-44.30-2.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.