Created attachment 928786 [details] ja_JP_volumes>bricks>add brick misalignment Description of problem: There is a misalignment in volumes>bricks>add brick pane for ja_JP and pt_BR locales. Here are the comments from the LMs: ja_JP:volumes #1 ykatabam Aug. 8, 2014, 11:52 a.m. In Add Bricks window, Japanese translation for the string "Allow bricks in root partition and re-use the bricks by clearing xattrs" is not aligned to the checkbox. It is placed below the checkbox. pt_BR: #1 ldelima Aug. 11, 2014, 9:34 a.m. In Volumes > Bricks > Add pop up screen The following message is not wrapped around the selection icon. Allow bricks in root partition and re-use the bricks by clearing xattrs Permitir bricks na partição root e usar novamente os bricks pela limpeza dos xattrs Please refer attached screen-shots. Version-Release number of selected component (if applicable): Red Hat Enterprise Virtualisationsmanager Version: 3.5.0-0.6.master.el6_5 How reproducible: always Steps to Reproduce: 1. please follow above mentioned steps. 2. 3. Actual results: The mentioned option is not aligned with the corresponding check-box. Expected results: The mentioned option and the check-box should be aligned. Additional info:
Created attachment 928787 [details] pt_BR>volumes>bricks misalignment
We currently do not support localization in RHSC, but will need this for hypercoverged use case. Retargeting to 3.6
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
oVirt 4.0 beta has been released, moving to RC milestone.
Can you please check if this issue is seen in 4.2?
Checked with 4.2.2.1-0.1.el7. Not observing it currently for any locales. Marking it as verified.
This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.7 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.
Closed by mistake, moving back to qa -> verified
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.0 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.