Bug 1512794 - [UI] - Add tooltip to the disabled default route role for clusters <=4.1
Summary: [UI] - Add tooltip to the disabled default route role for clusters <=4.1
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.2.0
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ovirt-4.2.1
: ---
Assignee: Ales Musil
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-14 06:36 UTC by Michael Burman
Modified: 2018-02-12 11:51 UTC (History)
1 user (show)

Fixed In Version: upstream 4.2.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-12 11:51:32 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.2+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 84584 0 master MERGED webadmin: Add tooltip to the disabled default route 2017-12-15 12:47:35 UTC
oVirt gerrit 84929 0 master MERGED webadmin: Add tooltip support into RadioboxCell 2017-12-15 12:46:48 UTC

Description Michael Burman 2017-11-14 06:36:09 UTC 
Description of problem:
[UI] - Add tooltip to the disabled default route role for clusters <=4.1 which will explain that the default route role can't be set/used for clusters <=4.1.

The tooltip should be added for both flows of the 'Manage Networks' dialog -
Network>Clusters flow - tooltip for the disabled checkbox/es
Cluster>Logical Networks flow - tooltip for the disabled radio button/s

Version-Release number of selected component (if applicable):
4.2.0-0.0.master.20171112130303.git8bc889c.el7.centos

How reproducible:
100

See also BZ 1481706
Comment 1 Michael Burman 2018-01-07 13:36:50 UTC 
Verified on - 4.2.1-0.2.el7
Comment 2 Sandro Bonazzola 2018-02-12 11:51:32 UTC 
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.