Bug 1469538 - Network changes to HE VM OVF take longer than other changes
Network changes to HE VM OVF take longer than other changes
Status: NEW
Product: ovirt-engine
Classification: oVirt
Component: BLL.HostedEngine (Show other bugs)
4.2.0
x86_64 Linux
low Severity medium (vote)
: ovirt-4.2.0
: ---
Assigned To: Doron Fediuck
meital avital
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-11 09:01 EDT by Artyom
Modified: 2017-10-25 05:34 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: SLA
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
dfediuck: ovirt‑4.2?
dfediuck: planning_ack?
dfediuck: devel_ack?
dfediuck: testing_ack?


Attachments (Terms of Use)

  None (edit)
Description Artyom 2017-07-11 09:01:17 EDT
Description of problem:
If I update HE VM CPU or memory, the engine straight forward updates the HE VM OVF(no need to wait for OvfUpdateIntervalInMinutes), I expect the same behavior when adding a NIC to HE VM.

Version-Release number of selected component (if applicable):
ovirt-engine-4.2.0-0.0.master.20170702100738.git46a9f67.el7.centos.noarch

How reproducible:
Always

Steps to Reproduce:
1. Deploy HE
2. Add master storage domain and wait for auto-import(and OVF generation)
3. Add a NIC to HE VM
4. Set global maintenance
5. Restart HE VM(hosted-engine --vm-start && hosted-engine --vm-poweroff)

Actual results:
New NIC does not exist under HE VM OS

Expected results:
New NIC exists under HE VM OS

Additional info:
If I wait for OvfUpdateIntervalInMinutes and restart HE VM, a NIC exists under HE VM OS

Note You need to log in before you can comment on or make changes to this bug.