Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

"User wants to be able to connect foreman bootiso when creating a new VM and boot from it as an alternative to PXE boot (they using vmware as virtualization platform.)

There is networks where PXE boot not is possible due to various reasons a good alternative to PXE boot would be to having foreman connect an foreman bootiso to the VM when it's created and boot from it instead."

Peter, what configuration method do you think is needed here?  I can think of the following, where a mixture might be best:

1. global setting to always use bootdisk for VMs that would otherwise PXE boot
2. per-compute resource setting
3. per-subnet setting
4. always use it if there's no DHCP and TFTP proxy on the subnet

(In reply to Dominic Cleal from comment #4)
> Peter, what configuration method do you think is needed here?  I can think
> of the following, where a mixture might be best:
> 
> 1. global setting to always use bootdisk for VMs that would otherwise PXE
> boot
> 2. per-compute resource setting
> 3. per-subnet setting
> 4. always use it if there's no DHCP and TFTP proxy on the subnet

Dominic, I think a mixture would be good:

1. global setting to always use bootdisk for VMs that would otherwise PXE boot
2. per-subnet setting
3. always use it if there's no DHCP and TFTP proxy on the subnet
4. Per-host setting, e.g. an checkbox when creating the host

Moving to 6.0.4 for QE purposes.

Upstream bug component is Bootdisk Plugin

Moving to POST since upstream bug http://projects.theforeman.org/issues/3287 has been closed
-------------
Anonymous
Applied in changeset commit:foreman_bootdisk|de59b7bba2ff16953fa6eaffef205000ec60aced.

*** Bug 1286702 has been marked as a duplicate of this bug. ***

Verified with sat6.3 GA snap25.

User can see new Provisioning method on UI under operating system tab while creating new host "Bootdisk based".

QE tested this feature on vmware compute-resource(Version 6.5.0.10000 Build 6671409). 

Please make sure that the user through which you'r trying to create host on vmware should have following permissions on "datastore" to upload bootdisk ISO, otherwise provisioning may fail at upload_iso step.

Datastore > Browse Datastore and Datastore > Low level file operations


Verification steps for Vmware:

1. Define a static subnet where no dhcp and tftp services are available
2. create host and select vmware compute-resource
3. Select Bootdisk based provisioning method
4. please select Nic type "vmxnet3 or e1000" from interfaces tab. QE tested both and both are working fine.
5. Make sure to select the checkbox "Add a CD-ROM drive to the virtual machine." from virtual machine tab.
6. when you submit the form, host will be created in vmware and will boot through auto attached ISO. Its a per-host bootdisk iso.

Created attachment 1357293 [details]
console logs while booting vm through bootdisk

@lzap: my understanding is that this feature only works with vmware and intend of this RFE is to cover only vmware CR ? I can see the changes in upstream PR are around vmware only. However, would like to get confirmation here please.

Yes that is correct.

Based on comments 16-20 moving this to verified.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:0336

Which port is used to autoattach image from satellite to vCenter .. is it port 443 form capsule or master ?

Hello, all VMWare requests go from Sat Server. This is the same for all compute resources unfortunately, we are tracking an RFE.

Thanks @lzap, so Port 443 I have to open from my Satellite Master -> vCenter.

Thanks,