Set network as first boot device for VMs in VMware compute resources
Compute resources - VMware
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
- Related to Feature #4317: Build button - Vmware provisioning - single click rebuild added
- Category changed from Compute resources to Compute resources - VMware
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..
- Status changed from New to Ready For Testing
- Assignee set to Timo Goebel
- Pull request https://github.com/theforeman/foreman/pull/2900 added
- Blocked by Feature #12479: Configure API revision for vSphere Compute Resource added
- Blocked by deleted (Feature #12479: Configure API revision for vSphere Compute Resource)
- Legacy Backlogs Release (now unused) set to 71
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Related to Bug #14160: VMware image-based provisioning: 'configSpec.bootOptions.bootOrder' parameter incorrect added
- Related to Bug #26010: For the vms built by Satellite 6 using "Network Based" installation mode on VMWare, unable to change the boot sequence via BIOS added
Also available in: Atom