Created attachment 1315984 [details] screenshot and rest request output Description of problem: When adding extra interface without IP settings, UI fills wrong IP values (v4 and v6). In my case, values taken from the previous default vNIC ('ovirtmgmt'). Version-Release number of selected component (if applicable): 4.2.0-0.0.master.20170818152502.gita8c361f.el7.centos How reproducible: 100% Steps to Reproduce: 1. Run VM with default vNIC (with ovirtmgmt network attached). 2. Create new network and attach it to the VM hoster. 3. Add vNIC with that new network to the VM. 4. Choose: Compute --> Virtual Machines --> VM --> Network Interfaces. Actual results: Wrong IP address is shown, REST/VM report completely different values. Expected results: Should report interface values from REST/VM.
This is a recent regression in the new UI. Alexander, could you take a look?
(In reply to Dan Kenigsberg from comment #1) > This is a recent regression in the new UI. Alexander, could you take a look? I moved some of the items to the verticals themselves. I believe this could be fixed without UX team. But we're here if you need assistance.
It is regression on the new UI. Another flow: 1) Create VM with 3 vNICs 2) Set ipv4 and ipv6 on each vNIC in the guest 3) Guest agent report 3 IPv4 and 3 ipv6 4) Go to vNICs sub tab and create new nic Result: The same ipv4 and ipv6 addresses reported for the new card on the NIC panel itself.
Created attachment 1319001 [details] record1
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Created attachment 1329481 [details] screen recording
Verified on ovirt-engine-4.2.0-0.0.master.20171009063348.gitf2b70a1.el7.centos.noarch
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.