Bug 1448698 - [downstream clone - 4.1.2] [TEXT] - Clarify 'Experimental' Switch Type on Cluster Settings
Summary: [downstream clone - 4.1.2] [TEXT] - Clarify 'Experimental' Switch Type on Clu...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.0.7
Hardware: x86_64
OS: Linux
high
low
Target Milestone: ovirt-4.1.2
: ---
Assignee: Martin Mucha
QA Contact: Meni Yakove
URL:
Whiteboard:
Depends On: 1438298
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-07 11:10 UTC by rhev-integ
Modified: 2020-04-15 15:35 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of: 1438298
Environment:
Last Closed: 2017-05-24 11:24:26 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:1280 0 normal SHIPPED_LIVE Red Hat Virtualization Manager (ovirt-engine) 4.1.2 2017-05-24 15:18:48 UTC
oVirt gerrit 75956 0 master MERGED webadmin: ovs renames 2017-05-07 11:11:36 UTC
oVirt gerrit 75957 0 ovirt-engine-4.1 MERGED webadmin: ovs renames 2017-05-07 11:11:36 UTC

Description rhev-integ 2017-05-07 11:10:43 UTC
+++ This bug is a downstream clone. The original bug is: +++
+++   bug 1438298 +++
======================================================================

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]

(Originally by Germano Veit Michel)

Comment 1 rhev-integ 2017-05-07 11:10:51 UTC
Created attachment 1268288 [details]
Screenshot for Claficiation

(Originally by Germano Veit Michel)

Comment 3 rhev-integ 2017-05-07 11:10:56 UTC
Martin, can we change the label of OVS to "OVS (experimental)"?

That would be more readable.

(Originally by danken)

Comment 5 rhev-integ 2017-05-07 11:11:05 UTC
Please also change legacy to 'Linux Bridge' as well.

(Originally by Yaniv Dary)

Comment 6 rhev-integ 2017-05-07 11:11:10 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

(Originally by rhev-integ)

Comment 7 rhev-integ 2017-05-07 11:11:15 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

(Originally by rhev-integ)

Comment 8 rhev-integ 2017-05-07 11:11:20 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

(Originally by rhev-integ)

Comment 9 rhev-integ 2017-05-07 11:11:25 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

(Originally by rhev-integ)

Comment 13 Michael Burman 2017-05-14 07:10:10 UTC
Verified on - 4.1.2.2-0.1.el7

Comment 15 errata-xmlrpc 2017-05-24 11:24:26 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-2017:1280


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