Steps to reproduce: 1) Install hosted engine environment with vNIC editing enabled (see the related bug) - set engine-config -s OvfUpdateIntervalInMinutes=1 2) Create new network dummynet in the DC/Cluster 3) Add a new vNIC to the hosted engine VM using dummynet and mark it as unplugged/down 4) Wait for the OVF to propagate to hosted engine OVF store (check step 1, it should take a minute) 5) Stop HE VM 6) Try to start the VM again Actual result: The VM will fail to start because of the vNIC. Expected result: The VM starts fine. Additional info: We have to convert the Linked xml element to linkActive VDSM's NIC device attribute.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Both gerrit links are merged - can this bug be moved to MODIFIED and be included in 3.6.5?
It will be.
Verified with ovirt-hosted-engine-ha-1.3.5.2-1.el7ev.noarch rhevm-3.6.5.3-0.1.el6.noarch according to steps in the description. The vm was started successfully with dummy nic still attached and unplugged as it was initially set.