Description of problem: Issuing a rhev pxe provision creates a vm with the incorrect boot order of 1.HD 2.Network and the virtual machine never picks up the pxe server. To summarize this issue. 1: VM provision started on CF 2: The VM get created on RHV ,and power it on 3: PXE/kick start didn't start on the VM. If the above is correct can you please try to create empty template on RHV side and set the boot sequence options 1: First Device: Network(PXE) 2: Second Device: HD RHEV 3.5 Version-Release number of selected component (if applicable): 5.6.2.2 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
@Josh: so, if I get you correctly the issue is that: - create a template and set the boot order of it to have 1st device network - provision a VM from this template using CF - the resulting VM does not have the netwrork as a first boot device If this is indeed the case, than you are hitting this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1340163 It will be fixed in 5.7.0
@Josh, just to be sure: did the overall PXE provisioning process fail or the only issue is that the VM is configured with 'hd' boot options? Because from my understanding the VM entity should have the boot options inherited from the template (i.e. 'hd' in the case of a 'Blank' template) and after that VM is created it should be provisioned using the "Run Once" functionality where the boot options will be overriden to 'network' just for the single run for the provisioning purposes. (meaning that rest api will report just the "permanent" configuration of 'hd' as the boot order) Is this the behavior you are observing or is something completely different happening?
With a template with the boot order set correctly (networking, hd) the vm boots up with HD first and never proceeds further in the pxe process.
@Josh if that is the case are you sure there is no problem with your particular PXE server? Maybe the boot proceeds with boot from hdd because it didn't manage to boot from network.
I've checked along with mbetak the PXE VM provision on different CFME versions, and here's what we've got: VM Provision from PXE problem was reproduced on CFME-5.6.2.2 & RHV-3.6.10 It was also reproduced on CFME-5.6.3.3 (latest CFME-5.6). The VM that was created on RHV, was NOT ran once & loaded from Network, as it should have. It was simply run, using the boot order it inherited from the RHV template. In the case we checked, template had a HDD, CDROM boot order, and the VM failed to load from those two. However, on CFME-5.7.0.17 (CFME-5.7 released on recent GA) & RHV-3.6.10, VM provision from PXE succeeded. VM was run once, loaded from Network, using the selected image, then after installation of the image finished, the VM was restarted, and was loaded OK from HDD. More details on the reproduce: ============================= All the above reproduce trials were done using the same RHV-3.6.10, RHV template, PXE server, custom template. After adding PXE server, and custom template, from Compute->Infrastructure->VMs & Templates-> Provision VMs: Chose a RHV RHEL6.3 template, provision from PXE image, and in the custom tab, I chose the custom template, and entered a password.
Tested VM PXE provision, same way as mentioned in comment #13, for CFME-5.7.1 & RHV-3.6.10, and it works well.
Created attachment 1247549 [details] automation logs tried with two different PXE servers.