Problem:
Ubuntu 22.04 host deployment fails with you need to load the kernel first
and no such device
before giving up. Partition with known EFI file not found
.
Expected outcome:
Successful boot of OS after deployment.
Foreman and Proxy versions:
Foreman 3.10.0
Distribution and version:
CentOS Stream 8
Other relevant data:
I seem to have made a little progress with this. If I boot into EFI setup, mode I see that the third option in the list is ubuntu and the second is the HD.
Manually selecting ubuntu immediately boots into the newly installed OS. So now I need to figure out why Subiquity fails to set the correct EFI boot option as the default.
The host is created on vSphere (7). If I set it to Force EFI setup
, it boots to this screen:
![image](https://community.theforeman.org/uploads/default/original/2X/0/083b75f326dde91685f6cd271429070d32d6e180.png)
Selecting ubuntu
or EFI Virtual disk (0.0)
here, boots the host into Ubuntu 22.04 successfully, but the EFI Network boot fails miserably (see first original post).
![image](https://community.theforeman.org/uploads/default/original/2X/3/3713d93851c22b11db184b19ac4c9844a87a1359.png)
![image](https://community.theforeman.org/uploads/default/original/2X/e/e0cc822fd2f773a0d63b3bf70be1da2bd314bd14.png)
![image](https://community.theforeman.org/uploads/default/original/2X/f/facf90135116e302c4633450534d997c1473491f.png)
Solution found, turns out to be a ‘bug’ between vSphere v7 and grub2: Unable to boot EFI Configured hosts post provisioning - #5 by stephenc
1 Like