2022-01-26 10:09:08 UTC
Triggering "setup machine" may not actually be carried out because the boot-order on the target machine is unknown by orthos.
While a system in BIOS mode may only lose its boot-order if someone changes it in the firmware, a system in UEFI mode will very likely boot from disk per default.
Some systems do indeed offer a way to influence the boot-order from remote to allow a true unattended reinstall. This happens to work on Dell systems via 'ipmitool chassis bootdev pxe' (perhaps also via 'chassis bootparam set bootflag force_pxe)', on HP iLO systems with 'ssh BMC onetimeboot netdev1'. Systems from Intel apparently lack such feature.
Orthos should have a way to trigger a "activate reinstall in cobbler; activate onetime-boot; force reboot" instead of the current "activate reinstall in cobbler; force reboot" on a per-platform level.
How such API will be actually implemented in cobbler should be discussed upstream.
Migrated from https://bugzilla.suse.com/show_bug.cgi?id=1195127
2022-01-26 10:09:08 UTC
Triggering "setup machine" may not actually be carried out because the boot-order on the target machine is unknown by orthos.
While a system in BIOS mode may only lose its boot-order if someone changes it in the firmware, a system in UEFI mode will very likely boot from disk per default.
Some systems do indeed offer a way to influence the boot-order from remote to allow a true unattended reinstall. This happens to work on Dell systems via 'ipmitool chassis bootdev pxe' (perhaps also via 'chassis bootparam set bootflag force_pxe)', on HP iLO systems with 'ssh BMC onetimeboot netdev1'. Systems from Intel apparently lack such feature.
Orthos should have a way to trigger a "activate reinstall in cobbler; activate onetime-boot; force reboot" instead of the current "activate reinstall in cobbler; force reboot" on a per-platform level.
How such API will be actually implemented in cobbler should be discussed upstream.
Migrated from https://bugzilla.suse.com/show_bug.cgi?id=1195127