Actions
Bug #20878
closed
VMware image-based provisioning: Rewrite boot order
Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - VMware
Target version:
Description
https://github.com/fog/fog-vsphere/pull/110 introduces the ability to change or rewrite the boot order for image based VMs.
We should use that feature, to rewrite the boot order so it's up to date with possible device changes during cloning.
In addition, we should prefer a boot from disk. A network boot can lead to booting the discovery image for example as no PXE config is written for the VM.
Updated by Timo Goebel over 6 years ago
- Related to Bug #14160: VMware image-based provisioning: 'configSpec.bootOptions.bootOrder' parameter incorrect added
Updated by Klaas D over 6 years ago
maybe we can just enforce the network boot for vms that are in build mode and disable it once install is done.
Updated by The Foreman Bot over 6 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/4831 added
Updated by Timo Goebel over 6 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 30e013191c708946e13b81051b7d18102a6384b4.
Updated by Marek Hulán over 6 years ago
- translation missing: en.field_release set to 296
Actions