Bug 1438298

Summary: [TEXT] - Clarify 'Experimental' Switch Type on Cluster Settings
Product: Red Hat Enterprise Virtualization Manager Reporter: Germano Veit Michel <gveitmic>
Component: ovirt-engineAssignee: Nobody <nobody>
Status: CLOSED ERRATA QA Contact: Michael Burman <mburman>
Severity: low Docs Contact:
Priority: high    
Version: 4.0.7CC: danken, eedri, lbopf, lsurette, mburman, myakove, rbalakri, Rhev-m-bugs, srevivo, ykaul, ylavi
Target Milestone: ovirt-4.2.0Keywords: EasyFix, ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
 Story Points: ---
Clone Of:
: 1448698 (view as bug list) Environment:
Last Closed: 2018-05-15 17:41:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1448698    
Attachments:
Description Flags
Screenshot for Claficiation none

Description Germano Veit Michel 2017-04-02 23:39:06 UTC 
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]
Comment 1 Germano Veit Michel 2017-04-02 23:42:44 UTC 
Created attachment 1268288 [details]
Screenshot for Claficiation
Comment 2 Dan Kenigsberg 2017-04-03 13:39:01 UTC 
Martin, can we change the label of OVS to "OVS (experimental)"?

That would be more readable.
Comment 4 Yaniv Lavi 2017-04-05 07:28:25 UTC 
Please also change legacy to 'Linux Bridge' as well.
Comment 5 rhev-integ 2017-04-26 08:44:21 UTC 
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
Comment 6 rhev-integ 2017-04-26 10:03:51 UTC 
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
Comment 7 rhev-integ 2017-04-26 10:49:23 UTC 
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
Comment 8 rhev-integ 2017-05-05 09:25:50 UTC 
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
Comment 10 Oved Ourfali 2017-05-07 11:13:11 UTC 
Bug is now cloned.
Can you move to ON_QA?
Comment 12 Michael Burman 2017-06-04 13:07:37 UTC 
Verified on - ovirt-engine-4.2.0-0.0.master.20170602194647.gitaf23eb5.el7.centos.noarch
Comment 16 errata-xmlrpc 2018-05-15 17:41:54 UTC 
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
Comment 17 Franta Kust 2019-05-16 13:04:57 UTC 
BZ<2>Jira Resync