Description of problem: After generating an UEFI bootable disk with osbuild-composer edge-simplified-installer, the os installation fails (one time failure). After coreos-installer-service disk reading finishes, the service coreos-installer-growfs.service shows the following failure message: [FAILED] Failed to start Grow root filesystem. See 'systemctl status coreos-installer-growfs.service' for details. [DEPEND] Dependency failed for Initrd Default Target. This seems to be a one time failure, that means, after rebooting the system, the failure message does not appear again and the installation seems to be ok. Version-Release number of selected component (if applicable): To generate UEFI bootable disk (edge-simplified-installer) osbuild-composer-87-1.el9.x86_64 osbuild-91-1.el9.noarch weldr-client-35.9-1.el9.x86_64 Bare Metal Hardware details: Onlogic HX401 How reproducible: 100% Steps to Reproduce: 1. Deploy RHEL-9.3 Openstack vm 2. git clone https://github.com/virt-s1/rhel-edge.git 3. Edit simplified blueprint to specify proper installation device $ vim ostree-simplified-installer.sh [customizations] - installation_device = "/dev/vda" + installation_device = "/dev/nvme0n1" 4. Generate iso UEFI bootable disk $ ./ostree-simplified-installer.sh 5. Write iso to bootable usb device $ sudo dd if=123456-simplified-installer.iso of=/dev/sdx bs=1M status=progress 6. Boot bare-metal hardware from usb device Actual results: Installation failing one time. Expected results: Installation ok Additional info: The experiment was repeat on another bare-metal hardware (Onlogic Karbon K410), that had /dev/sda as installation device name. The boot process and installation was successful. This experiment is part of the verification of bug https://bugzilla.redhat.com/show_bug.cgi?id=2177645
This should be a bug, because the nvme has different partition name, like nvme0n1p[0-9], compared with /dev/sda[0-9]. https://github.com/coreos/coreos-installer-dracut/blob/e3568c4be6b1db019b792fcd08323435b185c27a/dracut/scripts/coreos-installer-growfs#L30C24-L30C30 does not work with nvme disk partition. Here's example of nvme partition: ➜ cat /proc/partitions major minor #blocks name 259 0 1000204632 nvme0n1 259 1 524288 nvme0n1p1 259 2 1048576 nvme0n1p2 259 3 780519424 nvme0n1p3 259 4 209715200 nvme0n1p4 259 5 8388608 nvme0n1p5 252 0 8388608 zram0