Description of problem: In the Administration Portal, in Clusters -> Edit, we have "Switch Type(Experimental!)", which allows [Legacy|OVS]. The UI doesn't make it clear what is experimental: - Is it OVS? - Is is Legacy? - Is it switching from one to another? We know it's OVS, but it's not particularly clear to the customers who are not too familiar with RHV. OVS is indeed experimental, and in 4.0.7 it fails to add fresh host due to the known "non existent ovirtmgmt bridge" problem. Even if it works much better in 4.1, the UI should be clear that it is OVS that is experimental, not Legacy and not switching from one to another. Version-Release number of selected component (if applicable): ovirt-engine-4.0.7.4-0.1.el7ev.noarch And still the same on "latest" upstream: 4.1.1.6-1.el7 Actual results: "Switch Type(Experimental!)" : [OVS|Legacy] Expected results: "Switch Type" : [OVS (Experimental)|Legacy]
Created attachment 1268288 [details] Screenshot for Claficiation
Martin, can we change the label of OVS to "OVS (experimental)"? That would be more readable.
Please also change legacy to 'Linux Bridge' as well.
WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [FOUND CLONE FLAGS: ['rhevm-4.1.z', 'rhevm-4.2-ga'], ] For more info please contact: rhv-devops
Bug is now cloned. Can you move to ON_QA?
Verified on - ovirt-engine-4.2.0-0.0.master.20170602194647.gitaf23eb5.el7.centos.noarch
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-2018:1488
BZ<2>Jira Resync