Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1438298 - [TEXT] - Clarify 'Experimental' Switch Type on Cluster Settings
[TEXT] - Clarify 'Experimental' Switch Type on Cluster Settings
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
4.0.7
x86_64 Linux
high Severity low
: ovirt-4.2.0
: ---
Assigned To: nobody nobody
Michael Burman
: EasyFix, ZStream
Depends On:
Blocks: 1448698
  Show dependency treegraph
 
Reported: 2017-04-02 19:39 EDT by Germano Veit Michel
Modified: 2018-05-15 13:43 EDT (History)
12 users (show)

See Also:
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 13:41:54 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Network
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Screenshot for Claficiation (45.55 KB, image/png)
2017-04-02 19:42 EDT, Germano Veit Michel
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 75956 master MERGED webadmin: ovs renames 2017-04-25 09:47 EDT
oVirt gerrit 75957 ovirt-engine-4.1 MERGED webadmin: ovs renames 2017-04-25 11:46 EDT
Red Hat Product Errata RHEA-2018:1488 None None None 2018-05-15 13:43 EDT

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

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

Note You need to log in before you can comment on or make changes to this bug.