Description of problem: Due to the missing NetworkManager support in vdsm the Cockpit network page is disabled. Once vdsm gained the support the network page should be enabled again.
This should happen only after the 7.3.z clone of bug 1371126 is fixed.
Please require NetworkManager-1.4.0-13.el7_3 in rhv-h-4.0.6. Consider as a blocker.
Test version: redhat-virtualization-host-4.0-20161206.0 imgbased-0.8.11-0.1.el7ev.noarch cockpit-ws-122-3.el7.x86_64 NetworkManager-1.4.0-13.el7_3.x86_64 Test steps: 1. Install RHVH 2. Reboot RHVH and login cockpit 3. Focus on Networking page Test results: In step3, Networking page is enabled, can setup network via cockpit. So this bug is fixed in redhat-virtualization-host-4.0-20161206.0, change the status to VERIFIED.
Finally, we decided to disable cockpit network UI on 4.0.6 because some bugs(bug 1395108, bug 1400891, bug 1404120) were found during cockpit + NM + VDSM integration testing on build redhat-virtualization-host-4.0-20161206.0.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Current plan is to support running side by side with NM only in 4.1. If this is found to be safe, can consider backporting to 4.0.z
Not a blocker, postponed to 4.1.1
This is currently enabled. Leaving on 4.1.1 for now. Will move to ON_QA once a decision is reached about keeping this.
Test version: redhat-virtualization-host-4.1-20170222.0 imgbased-0.9.13-0.1.el7ev.noarch cockpit-ws-126-1.el7.x86_64 NetworkManager-1.4.0-14.el7_3.x86_64 Test steps: 1. Install redhat-virtualization-host-4.1-20170222.0 2. Reboot RHVH and login cockpit 3. Focus on Networking page Test results: In step3, Networking page is enabled, can setup network via cockpit. So this bug is fixed in redhat-virtualization-host-4.1-20170222.0, change the status to VERIFIED.
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://access.redhat.com/errata/RHEA-2017:1114