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
verified on: ovirt-hosted-engine-setup-2.2.10-1.el7ev.noarch ovirt-hosted-engine-ha-2.2.5-1.el7ev.noarch tested according to the described steps and verified that after adding of the NIC to the HE VM it appears under OS. also after restart (hosted-engine --vm-poweroff/startup) [root@compute-ge-he-1 ~]# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:1a:4a:16:10:9f brd ff:ff:ff:ff:ff:ff inet 10.35.92.159/22 brd 10.35.95.255 scope global noprefixroute dynamic eth0 valid_lft 43073sec preferred_lft 43073sec inet6 2620:52:0:235c:21a:4aff:fe16:109f/64 scope global mngtmpaddr dynamic valid_lft 2591920sec preferred_lft 604720sec inet6 fe80::21a:4aff:fe16:109f/64 scope link valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:1a:4a:16:10:46 brd ff:ff:ff:ff:ff:ff
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.