Bug 1659099

Summary: [UI] Can't see the whole IPv6 address
Product: [oVirt] ovirt-engine Reporter: Roni <reliezer>
Component: BLL.NetworkAssignee: Ales Musil <amusil>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: low Docs Contact:
Priority: high    
Version: 4.3.0CC: bugs
Target Milestone: ovirt-4.3.2Flags: rule-engine: ovirt-4.3+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.3.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-19 10:03:21 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
UI IPv6 address edit box none

Description Roni 2018-12-13 14:58:59 UTC
Created attachment 1514089 [details]
UI IPv6 address edit box

Description of problem:
Can't see the whole IPv6 address at the web UI due to short edit/text box


Version-Release number of selected component (if applicable):
4.3.0-0.6.alpha2.el7

How reproducible:
100%

Steps to Reproduce:
1. Engine UI: go to Compute | Hosts 
2. Click any host name | Network Interfaces tab | Setup Host Networks button
3. Edit the 'ovirtmgmt' attached to the NIC
4. Go to the IPv6 tab | click the Static radio-button, or any other 
   radio-button


Actual results:
The edit/text box is too short that you can't see the whole IPv6 address

Expected results:
The whole IPv6 address should be seeing

Additional info:
See attached UI capture

Comment 1 Michael Burman 2019-03-03 13:50:22 UTC
Verified upstream on - 4.3.1.2-0.0.master.20190226172724.git8186eb5.el7

Comment 2 Raz Tamir 2019-03-05 21:30:25 UTC
QE verification bot: the bug was verified upstream

Comment 3 Sandro Bonazzola 2019-03-19 10:03:21 UTC
This bugzilla is included in oVirt 4.3.2 release, published on March 19th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.2 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.