Bug 1542097

Summary: [ALL_LANG] Text "Reboot host after upgrade" is misaligned with checkbox at compute > hosts > installation > Upgrade
Product: [oVirt] ovirt-engine Reporter: vishal vijayraghavan <vvijayra>
Component: Frontend.WebAdminAssignee: Ravi Nori <rnori>
Status: CLOSED CURRENTRELEASE QA Contact: Lucie Leistnerova <lleistne>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2.1CC: bbarve, bugs, gshereme, lleistne, lsvaty, lveyde, mperina, vvijayra
Target Milestone: ovirt-4.2.2Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.2.2.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-29 11:07:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
host upgrade reboot text none

Description vishal vijayraghavan 2018-02-05 14:47:40 UTC
Created attachment 1391557 [details]
host upgrade reboot text

Description of problem:
For all locales including English, Text "Reboot host after upgrade" is misaligned with checkbox at 
compute > hosts > installation > Upgrade

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

How reproducible:
Always

Steps to Reproduce:
1.login to admin portal.
2.go to compute > hosts > installation > Upgrade.
3.observe the text "Reboot host after upgrade".


Actual results:
Text "Reboot host after upgrade" is misaligned

Expected results:
Text "Reboot host after upgrade" should not be misaligned

Additional info:

Comment 2 Lucie Leistnerova 2018-02-23 08:12:52 UTC
checkbox text well formatted in all lang

verified in ovirt-engine-webadmin-portal-4.2.2.1-0.1.el7.noarch

Comment 3 Sandro Bonazzola 2018-03-29 11:07:54 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.