Project

General

Profile

Bug #20878

VMware image-based provisioning: Rewrite boot order

Added by Timo Goebel about 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - VMware
Target version:
Difficulty:
easy
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

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.


Related issues

Related to Foreman - Bug #14160: VMware image-based provisioning: 'configSpec.bootOptions.bootOrder' parameter incorrectClosed2016-03-11

Associated revisions

Revision 30e01319 (diff)
Added by Timo Goebel about 3 years ago

fixes #20878 - vmware clone: rewrite boot order

History

#1 Updated by Timo Goebel about 3 years ago

  • Related to Bug #14160: VMware image-based provisioning: 'configSpec.bootOptions.bootOrder' parameter incorrect added

#2 Updated by Klaas D about 3 years ago

maybe we can just enforce the network boot for vms that are in build mode and disable it once install is done.

#3 Updated by The Foreman Bot about 3 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/4831 added

#4 Updated by Timo Goebel about 3 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#5 Updated by Marek Hulán about 3 years ago

  • Legacy Backlogs Release (now unused) set to 296

Also available in: Atom PDF