Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: After going through the firstboot menus, the final step (install and reboot) fails. This is due to there not being a /dev/disk/by-label entry for the Boot partition. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Configure node through firstboot 2.Choose install and reboot option 3. Actual results: Fails Expected results: Installs and reboots Additional info: from ovirt.log: Current kernel boot parameters are: console=tty1 console=ttyS0,115200n8 ovirt_standalone Please enter kernel boot arguments (hit return to use the above): Do you wish to continue ([Y]es/[N]o)? y Mar 09 18:20:17 installing the image. Mar 09 18:20:17 unable to determine Root partition ERROR: Local install and reboot FAILED. See /var/log/ovirt.log
(In reply to comment #0) > After going through the firstboot menus, the final step (install and reboot) > fails. This is due to there not being a /dev/disk/by-label entry for the Boot > partition. Instead of relying on by-label symlink, mount LABEL=BOOT should be used.
I've changed the ovirt_function to mount LABEL=Boot, but the issue stems from the iscsi boot changes. It appears that we create a partition with LABEL=Boot only if we are using iscsi for the boot device. I might be reading this wrong, but when using iscsi, it looks like we end up with the following partitions: 1. LABEL=Boot on iscsi drive 2. LABEL=Root on ROOTDRIVE 3. LABEL=RootBackup on ROOTDRIVE 4. LVM on HOSTVGDRIVE (which might = ROOTDRIVE) Need to understand if we need all these or if the Root and Boot are redundant
Created attachment 402334 [details] Patch
Fixed in upstream ovirt node 1.9.1