Bug 1522784

Summary: [UI] - Network role icons are overlapping the network's name in case of long name or vlan tagged
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.NetworkAssignee: Ales Musil <amusil>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: low Docs Contact:
Priority: low    
Version: 4.2.0CC: bugs
Target Milestone: ovirt-4.2.1Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-12 11:54:26 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:
Attachments:
Description Flags
screenshots none

Description Michael Burman 2017-12-06 12:58:39 UTC
Created attachment 1363659 [details]
screenshots

Description of problem:
[UI] - Network role icons are overlapping the network's name in case of long name or vlan tagged.

If our management network has a long name and it's also a vlan tagged network, then the network's tooltip in the setup networks dialog will show the network role icons overlapping the network's name and it doesn't look so good.

Version-Release number of selected component (if applicable):
4.2.1-0.0.master.20171205151153.git71bd47e.el7.centos

How reproducible:
100

Steps to Reproduce:
1. Create management network called new-default tagged with vlan 162 for example
2. Add host to webadmin and go to setup networks dialog

Actual results:
Network role icons overlapping the network's name

Comment 1 Michael Burman 2017-12-18 07:39:29 UTC
Verified on - 4.2.1-0.0.master.20171215201518.gite23b568.el7.centos

Comment 2 Sandro Bonazzola 2018-02-12 11:54:26 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.