Bug #5510
closedSet network as first boot device for VMs in VMware compute resources
Description
When creating a virtual machine via Foreman on a VMware compute resource (ESX), the boot order of the VM has the hard disk as first boot device and network as last boot device.
This works for the first VM build because there's nothing on the VM HDD, but when you try to rebuild the VM the PXE image is never loaded from the network because the installed OS is booted first from HDD.
Somehow the default boot order should have network set as the first boot device, just like it happens for other compute resource types, e.g. libvirt/KVM.
This would also partly satisfy this feature request: http://projects.theforeman.org/issues/4317
Updated by Arnold Bechtoldt almost 10 years ago
We see this issue in several of our projects. It would be great to have solution for this. A workaround would be to change the boot priority order after adding the host via hooks or sth. similar..
Updated by Anonymous about 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset b466551bddca3ac3638d90eae508711c10e287e1.