Bug 1398205

Summary: The GUI only shows custom roles if they are in the default plan
Product: Red Hat OpenStack Reporter: Udi Kalifon <ukalifon>
Component: openstack-tripleo-uiAssignee: Jiri Tomasek <jtomasek>
Status: CLOSED ERRATA QA Contact: Ola Pavlenko <opavlenk>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 10.0 (Newton)CC: apannu, jjoyce, jpichon, jschluet, jtomasek, rhel-osp-director-maint, sclewis, slinaber, tvignaud
Target Milestone: gaKeywords: Triaged
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-ui-1.0.5-2.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-14 16:34:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1398274    

Description Udi Kalifon 2016-11-24 09:51:37 UTC
Description of problem:
I uploaded new templates with custom roles, and the GUI didn't display them. It turns out that custom roles are only displayed if they are in the default plan, and the current plan is ignored.

There is a fix for it upstream, and we need to make sure it is merged downstream for the GA: https://review.openstack.org/#/c/401351/


How reproducible:
100%


Steps to Reproduce:
1. Create custom roles and upload the templates
2. Switch to the new plan and make it the active plan
3. The deployment page still shows the same roles as always

Comment 1 Jiri Tomasek 2016-11-24 09:54:11 UTC
Upstream bug: https://bugs.launchpad.net/tripleo/+bug/1644310

Comment 6 Udi Kalifon 2016-12-08 08:25:25 UTC
Verified in the RC puddle 2016-11-30.9

Comment 7 Anandeep Pannu 2016-12-09 21:05:48 UTC
Since this is verified - clearing needinfo

Comment 9 errata-xmlrpc 2016-12-14 16:34:59 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://rhn.redhat.com/errata/RHEA-2016-2948.html