Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1696622 - [ALL_LANG] The upgrade screens on compute -> cluster screens are unlocalized
Summary: [ALL_LANG] The upgrade screens on compute -> cluster screens are unlocalized
Keywords:
Status: NEW
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.3.0
Hardware: All
OS: Linux
medium
medium vote
Target Milestone: ovirt-4.3.4
: ---
Assignee: Scott Dickerson
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-05 09:41 UTC by Bhushan Barve
Modified: 2019-04-08 15:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
oVirt Team: UX
pm-rhel: ovirt-4.3?
bbarve: planning_ack?
bbarve: devel_ack?


Attachments (Terms of Use)
unlocalized_1 (deleted)
2019-04-05 09:41 UTC, Bhushan Barve
no flags Details
unlocalized_2 (deleted)
2019-04-05 09:42 UTC, Bhushan Barve
no flags Details

Description Bhushan Barve 2019-04-05 09:41:56 UTC
Created attachment 1552343 [details]
unlocalized_1

Description of problem: For all languages, the upgrade page screens on compute -> cluster are unlocalized. Please refer attached screenshots.


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

How reproducible:
always

Steps to Reproduce:
1. login to the admin portal with any locale other than English
2. Go to compute -> cluster
3. select a cluster and click on upgrade button.

Actual results:
The upgrade screens are not localized.

Expected results:
All the text on these screens should be localized.

Additional info:

Comment 1 Bhushan Barve 2019-04-05 09:42:21 UTC
Created attachment 1552344 [details]
unlocalized_2


Note You need to log in before you can comment on or make changes to this bug.