Description: Already selected "PXE Boot Engine VM" via Hosted Engine TUI, but during HE deployment, here still ask to specify the device to boot the VM. Version: # rpm -qa ovirt-node-plugin-hosted-engine ovirt-hosted-engine-setup ovirt-hosted-engine-setup-1.3.0-1.el7ev.noarch ovirt-node-plugin-hosted-engine-0.3.0-3.el7ev.noarch # cat /etc/redhat-release Red Hat Enterprise Virtualization Hypervisor (Beta) release 7.2 (20151112.1.el7ev) Test Steps: 1. Installed RHEVH 7.2 for rhev 3.6 beta 1 successful. 2. Setup Network via dhcp yet. 3. Set root password on Engine TUI. 3. Deploy HE on RHEV-H TUI. 4. Enable "PXE Boot Engine VM" 5. Click on "Deploy" ... --== VM CONFIGURATION ==-- Please specify the device to boot the VM from (choose disk for the oVirt engine appliance) (cdrom, disk, pxe) [disk]: pxe Please specify an alias for the Hosted Engine image [hosted_engine]: The following CPU types are supported by this host: - model_SandyBridge: Intel SandyBridge Family - model_Westmere: Intel Westmere Family - model_Nehalem: Intel Nehalem Family - model_Penryn: Intel Penryn Family - model_Conroe: Intel Conroe Family ... Actually Result: During VM Configuration, still ask to specify the device to boot the VM, here already selected the PXE Boot Engine VM via Hosted Engine TUI yet. Expected Result: HE TUI already selected PXE Boot Engine VM, don't need to ask to specify the device to boot the VM again.
Created attachment 1095224 [details] sosreport
Verified the bug rhev-hypervisor7-7.2-20151201.2(ovirt-node-plugin-hosted-engine-0.3.0-4.el7ev) Test Steps: 1. Installed rhev-hypervisor7-7.2-20151201.2 successful. 2. Setup Network via dhcp yet. 3. Set root password on Engine TUI. 3. Deploy HE on RHEV-H TUI. 4. Enable "PXE Boot Engine VM" 5. Click on "Deploy" Result: Don't need to ask to specify the device to boot the VM because TUI has selected PXE boot VM.
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://rhn.redhat.com/errata/RHBA-2016-0378.html