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

Bug 1694740

Summary: Hosted Engine disks content types are showing unlocalized in the disks tab
Product: [oVirt] ovirt-engine Reporter: Tal Nisan <tnisan>
Component: Frontend.WebAdminAssignee: Tal Nisan <tnisan>
Status: CLOSED CURRENTRELEASE QA Contact: Evelina Shames <eshames>
Severity: high Docs Contact:
Priority: unspecified    
Version: futureCC: aefrat, bugs, eshenitz, sfishbai
Target Milestone: ovirt-4.3.3Flags: pm-rhel: ovirt-4.3+
tnisan: blocker?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.3.3.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-16 13:58:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot none

Description Tal Nisan 2019-04-01 14:11:43 UTC 
Description of problem:
4 new types of disks content types related to Hosted Engine were added to oVirt 4.3.3, they appear unlocalized in the disks main tab

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. In Webadmin go to the disk main tabs
2.
3.

Actual results:
Disk content types unlocalized

Expected results:
Disk content types localized

Additional info:
Comment 1 Tal Nisan 2019-04-01 14:36:29 UTC 
Created attachment 1550568 [details]
Screenshot
Comment 2 Shir Fishbain 2019-04-07 13:38:35 UTC 
Verified
Disk content types localized

vdsm-4.30.12-1.el7ev.x86_64
ovirt-engine-4.3.3.2-0.1.el7.noarch
Comment 3 Tal Nisan 2019-04-08 13:31:29 UTC 
*** Bug 1694940 has been marked as a duplicate of this bug. ***
Comment 4 Sandro Bonazzola 2019-04-16 13:58:19 UTC 
This bugzilla is included in oVirt 4.3.3 release, published on April 16th 2019.

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