Bug 1435172

Summary: Entities menu does not contain Pod object
Product: Red Hat CloudForms Management Engine Reporter: Tony <ashlifst>
Component: UI - OPSAssignee: Nimrod Shneor <nshneor>
Status: CLOSED ERRATA QA Contact: Einat Pacifici <epacific>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.8.0CC: cben, hkataria, jhardy, mpovolny, obarenbo, simaishi
Target Milestone: GA   
Target Release: 5.8.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: container
Fixed In Version: 5.8.0.8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-31 14:43:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Container Management Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Map Tags - entity menu none

Description Tony 2017-03-23 10:21:20 UTC 
Created attachment 1265671 [details]
Map Tags - entity menu

Description of problem:


In CFME, Configuration ---> CFME Region ---> Map Tags ---> Add ---> Click on Entity dropdown menu.


Expected result: 


Pod should be among the menu options


Actual result:

Pod is not included in the menu options


Reference:

https://bugzilla.redhat.com/show_bug.cgi?id=1383405
Comment 2 Nimrod Shneor 2017-03-27 11:48:46 UTC 
This is solved in the following PR: 
https://github.com/ManageIQ/manageiq-ui-classic/pull/780

We have "Pod" as the *English* translation of "ContainerGroup" - recent changes around label->tag mapping broke the translation – the `ui_lookup()` call - and this PR should fix it.
Comment 3 Nimrod Shneor 2017-03-27 11:50:22 UTC 
Just to verify I fetched the branch and saw it did fix this.
Comment 4 Beni Paskin-Cherniavsky 2017-03-27 20:31:36 UTC 
https://github.com/ManageIQ/manageiq-ui-classic/pull/780 merged.
Comment 5 Tony 2017-04-05 10:15:15 UTC 
Verified on CFME 5.8.0.8
Comment 7 errata-xmlrpc 2017-05-31 14:43:48 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:1367