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

Bug 1679888

Summary: [ja_JP,fr_FR, de_DE] Misalignment issue on Storage> Volumes> Bricks >add window.
Product: [oVirt] ovirt-engine Reporter: Pooja Yadav <poyadav>
Component: Frontend.WebAdminAssignee: Kaustav Majumder <kmajumde>
Status: CLOSED DUPLICATE QA Contact: Lukas Svaty <lsvaty>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.3.0CC: bugs, godas, gshereme, sabose
Target Milestone: ovirt-4.4.0Keywords: i18n
Target Release: ---Flags: pm-rhel: ovirt-4.4+
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-09 10:25:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
fr_FR alignment for Storage> Volumes> Bricks >add window. none

Description Pooja Yadav 2019-02-22 07:10:06 UTC
Created attachment 1537363 [details]
fr_FR alignment for Storage> Volumes> Bricks >add window.

Description of problem:
Text not aligned with the checkbox for fr_FR, ja_JP, de_DE locale on Storage> Volumes> Bricks >add window.

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

How reproducible:
always

Steps to Reproduce:
1. Login to admin portal with any locale mentioned above
2. Go to Storage> Volumes> Bricks >add window.
3. Observe the UI alignment for "Allow bricks in root partition and re-use the bricks by clearing xattrs" option.

Actual results:
Text not aligned with the check box.

Expected results:
Text should be aligned with the check box.

Additional info:
Please refer screenshot.

Comment 1 Gobinda Das 2019-10-09 10:25:36 UTC
Closing this as all alignment issue fixed in https://bugzilla.redhat.com/show_bug.cgi?id=1679880

*** This bug has been marked as a duplicate of bug 1679880 ***