-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.18.z
-
None
Description of problem:
Test pxe boot in ABI day2 install, day2 host can not reboot from the disk properly, but reboot from pxe again. This is not reproduced in all hosts and reboots.
Version-Release number of selected component (if applicable):
4.18.0-0.nightly-2024-11-26-075648
How reproducible:
Not always, about 70% in amd64 and 100% in arm64
Steps to Reproduce:
1. Run ABI day1 install booting from pxe 2. After day1 cluster is installed, run ABI day2 install booting from pxe 3. Day2 host hasn't reboot from disk as expected, but reboot from pxe again. From agent.service log, we can see the error: level=info msg=\"SetBootOrder, runtime.GOARCH: amd64, device: /dev/sda\"\ntime=\"2024-11-27T06:48:15Z\" level=info msg=\"Setting efibootmgr to boot from disk\"\ntime=\"2024-11-27T06:48:15Z\" level=error msg=\"failed to find EFI directory\" error=\"failed to mount efi device: failed executing /usr/bin/nsenter [--target 1 --cgroup --mount --ipc --pid -- mount /dev/sda2 /mnt], Error exit status 32, LastOutput \\\"mount: /var/mnt: special device /dev/sda2 does not exist.\\\"\"\ntime=\"2024-11-27T06:48:15Z\" level=warning msg=\"Failed to set boot order\" error=\"failed to mount efi device: failed executing /usr/bin/nsenter [--target 1 --cgroup --mount --ipc --pid -- mount /dev/sda2 /mnt], Error exit status 32
Actual results:
Day2 host hasn't reboot from disk as expected
Expected results:
Day2 host should reboot from disk to complete the installation
Additional info: