Bug 2449340

Summary: Anaconda crashes on custom install with /home on secondary drive
Product: [Fedora] Fedora Reporter: Nyalnara <lysarion>
Component: anaconda-webuiAssignee: Katerina Koukiou <kkoukiou>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 43CC: alpha, anaconda-maint, kkoukiou, mkolman, rvykydal, w
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-05-05 15:18:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
install log
none
Screenshot 1
none
Screenshot 2 none

Description Nyalnara 2026-03-19 23:23:55 UTC
Anaconda crashes when finalizing installation of custom installation with /home on separate drive, seems to fail to get separate drive.

Message error is "Le programme d'installation ne peut pas continuer en raison d'une erreur critique : Installation of the system failed: Enregistrement des fichiers de configuration et kickstart", details given are "org.fedoraproject.Anaconda.Error: 'NoneType' object has no attribute 'path'".

Looking at `/tmp/journal.log`, it seems Anaconda.Modules.Storage fails to find the disk that it just managed to format properly earlier:

```
Mar 19 22:37:52 localhost-live org.fedoraproject.Anaconda.Modules.Storage[5450]: DEBUG:blivet:               DeviceTree.get_device_by_device_id: device_id: BTRFS-00ed7298-89f5-4ee4-9044-c0da8c17b9dd ; incomplete: False ; hidden: False ;
Mar 19 22:37:52 localhost-live org.fedoraproject.Anaconda.Modules.Storage[5450]: DEBUG:blivet:               DeviceTree.get_device_by_device_id returned None

```

Custom install was basically:
- system SSD
  - 2 GiB /boot/efi
  - 16 GiB swap
  - everything else as btrfs /
- home SSD, btrfs

Partition scheme had already been created previously, but partition were formatted as part of the install process.

Full log will be included as attachment.

Reproducible: Always

Steps to Reproduce:
1. boot to live-USB
2. begin the graphical install process
3. when prompted for the install target, select both disks, then choose to manually assign mount points (see screenshot 1)
4. assign mount points with /home on the second disk (see screenshot 2)
Actual Results:
Installer crash before creating the user, subsequent boot bring up the user creation process for a first boot with no user. Also settings (specific keyboard layout) are not properly set (as that require the user existing at the end of the installation process). 

Expected Results:
User should have been properly created.

Comment 1 Nyalnara 2026-03-19 23:25:09 UTC
Created attachment 2134182 [details]
install log

Comment 2 Nyalnara 2026-03-19 23:26:09 UTC
Created attachment 2134183 [details]
Screenshot 1

Comment 3 Nyalnara 2026-03-19 23:26:37 UTC
Created attachment 2134184 [details]
Screenshot 2

Comment 4 Katerina Koukiou 2026-05-05 15:18:12 UTC

*** This bug has been marked as a duplicate of bug 2394554 ***