Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1434398

Summary: Text in UI window "New External Subnet" does not look normal
Product: [oVirt] ovirt-provider-ovn Reporter: Mor <mkalfon>
Component: providerAssignee: Marcin Mirecki <mmirecki>
Status: CLOSED CURRENTRELEASE QA Contact: Mor <mkalfon>
Severity: medium Docs Contact:
Priority: low    
Version: unspecifiedCC: bugs, danken, myakove, ylavi
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
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:45:40 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 Mor 2017-03-21 12:32:43 UTC
Created attachment 1265050 [details]
screenshot

Description of problem:
1. First line text doesn't fit with next items.
2. Padding of text items in this window does not look normal.

Version-Release number of selected component (if applicable):
Red Hat Virtualization Manager Version: 4.1.1.5-0.1.el7

How reproducible:
100%

Steps to Reproduce:
1. Create OVN network without subnet.
2. Networks --> Select the network --> Subnets tab --> Create new subnet.

Actual results:
Window doesn't look normal.

Expected results:
Window should look normal.

Additional info:
Please ignore purple and green colors in the screenshot (they are related to other bugs).

Comment 1 Mor 2017-06-05 10:52:08 UTC
Verified on oVirt master branch: 4.2.0-0.0.master.20170602194647.gitaf23eb5.el7.centos

PLEASE NOTE: this is not yet verified with Red Hat Virtualization Manager Version: 4.1.1.5-0.1.el7 where I originally found the bug.

Comment 2 Sandro Bonazzola 2017-12-20 11:45:40 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.