Bug 1478688

Summary: [UI] - Adjust setup networks dialog to display long names networks
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.NetworkAssignee: Ales Musil <amusil>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.1.5.1CC: bugs, danken
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
Target Release: 4.2.0   
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: 2017-12-20 11:42:01 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
screenshot none

Description Michael Burman 2017-08-06 06:21:02 UTC
Created attachment 1309584 [details]
screenshot

Description of problem:
[UI] - Adjust setup networks dialog to display long names networks.

Currently the setup networks dialog is broken when long names networks are exist in the DC or attached to the host. See screenshot attached

Version-Release number of selected component (if applicable):
4.1.5.1-0.1.el7

How reproducible:
100

Steps to Reproduce:
1. Create long name network(more then 50 characters)
2. Open the setup networks dialog

Actual results:
The dialog is broken

Expected results:
We should adjust the dialog to display long networks

Comment 1 Michael Burman 2017-11-13 08:52:23 UTC
Verified on - 4.2.0-0.0.master.20171112130303.git8bc889c.el7.centos

The setup networks dialog no longer broken if long name network is attached to the cluster, the long name is dotted and the full name is displayed in the network's tooltip. Looks much better now)

Comment 2 Sandro Bonazzola 2017-12-20 11:42:01 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.