Project

General

Profile

Bug #5510

Set network as first boot device for VMs in VMware compute resources

Added by Marco De Vitis over 5 years ago. Updated about 1 year ago.

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

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


Related issues

Related to Foreman - Feature #4317: Build button - Vmware provisioning - single click rebuildResolved2014-02-11
Related to Foreman - Bug #14160: VMware image-based provisioning: 'configSpec.bootOptions.bootOrder' parameter incorrectClosed2016-03-11
Related to Foreman - Bug #26010: For the vms built by Satellite 6 using "Network Based" installation mode on VMWare, unable to change the boot sequence via BIOSNew
Blocked by Foreman - Refactor #12612: Update fog to 1.37.0Closed2015-11-26

Associated revisions

Revision b466551b (diff)
Added by Timo Goebel over 3 years ago

fixes #5510 - Set network as first boot device for VMs in VMware compute resources

History

#1 Updated by Dominic Cleal over 5 years ago

  • Related to Feature #4317: Build button - Vmware provisioning - single click rebuild added

#2 Updated by Dominic Cleal almost 5 years ago

  • Category changed from Compute resources to Compute resources - VMware

#3 Updated by Arnold Bechtoldt over 4 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..

#4 Updated by The Foreman Bot almost 4 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Timo Goebel
  • Pull request https://github.com/theforeman/foreman/pull/2900 added

#5 Updated by Timo Goebel almost 4 years ago

  • Blocked by Feature #12479: Configure API revision for vSphere Compute Resource added

#6 Updated by Timo Goebel almost 4 years ago

  • Blocked by deleted (Feature #12479: Configure API revision for vSphere Compute Resource)

#7 Updated by Timo Goebel over 3 years ago

#8 Updated by Dominic Cleal over 3 years ago

  • Legacy Backlogs Release (now unused) set to 71

#9 Updated by Anonymous over 3 years ago

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

#10 Updated by Dominic Cleal over 3 years ago

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

#11 Updated by Marek Hulán 7 months ago

  • 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 PDF