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

Bug 1542900

Summary: [fr, zh_CN, ko] UI alignment needs to be corrected on compute -> data centers -> logical networks -> new -> vNIC profiles page.
Product: [oVirt] ovirt-engine Reporter: Bhushan Barve <bbarve>
Component: Frontend.WebAdminAssignee: Ales Musil <amusil>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Matyáš <pmatyas>
Severity: medium Docs Contact:
Priority: low    
Version: 4.2.1CC: bbarve, bugs, gshereme, lsvaty, pmatyas, ylavi
Target Milestone: ovirt-4.2.2Keywords: i18n
Target Release: ---Flags: ylavi: ovirt-4.2+
ylavi: exception+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-29 11:09:20 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
ko_KR_vNIC profile none

Description Bhushan Barve 2018-02-07 10:12:52 UTC
Created attachment 1392589 [details]
ko_KR_vNIC profile

Description of problem: For fr, zh_CN and ko locales the UI alignment on compute -> data centers -> logical networks -> new -> vNIC profiles page looks improper. The text and the dropdown is not aligned properly. Please refer attached screenshot.


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

How reproducible:
always

Steps to Reproduce:
1. Login with any of the mentioned locales to admin portal 
2. Go to compute -> data centers -> logical networks -> new -> vNIC profiles
3. Observe the UI elements

Actual results:
 The UI elements need to be aligned properly. The dropdown and the text fall on different line.

Expected results:
The UI alignment should be proper.

Additional info:

Comment 2 Petr Matyáš 2018-03-06 09:20:31 UTC
Verified on ovirt-engine-4.2.2.2-0.1.el7.noarch

Comment 3 Sandro Bonazzola 2018-03-29 11:09:20 UTC
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

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