Bug 1659099 - [UI] Can't see the whole IPv6 address
Summary: [UI] Can't see the whole IPv6 address
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.3.0
Hardware: x86_64
OS: Linux
high
low
Target Milestone: ovirt-4.3.2
: ---
Assignee: Ales Musil
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-13 14:58 UTC by Roni
Modified: 2019-03-19 10:03 UTC (History)
1 user (show)

Fixed In Version: ovirt-engine-4.3.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-19 10:03:21 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.3+

Attachments (Terms of Use)
UI IPv6 address edit box (85.80 KB, image/png)
2018-12-13 14:58 UTC, Roni 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 97925 0 master MERGED webadmin: Fix visibility of IPv6 address 2019-02-21 12:32:04 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.