Bug 1588434

Summary:	[UI] Clicking Manage roles fails to load role list if overcloud plan is deleted
Product:	Red Hat OpenStack	Reporter:	Gurenko Alex <agurenko>
Component:	openstack-tripleo-common	Assignee:	Jason E. Rist <jrist>
Status:	CLOSED ERRATA	QA Contact:	Arik Chernetsky <achernet>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	13.0 (Queens)	CC:	dtrainor, jjoyce, jschluet, mburns, slinaber, tvignaud
Target Milestone:	ga	Keywords:	Triaged
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-common-8.6.1-20.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-27 13:57:12 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:

Description Gurenko Alex 2018-06-07 10:51:55 UTC

Description of problem: It's not possible to manage roles if you don't have plan called overcloud.


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


How reproducible: 100%


Steps to Reproduce:
1. Login to UI
2. Delete plan called overcloud
3. Upload a new plan with a different name
4. Click Manage Roles inside new plan

Actual results:

Error message shows that Roles cannot be loaded


Expected results:

List of roles displayed


Additional info:

Comment 1 Jason E. Rist 2018-06-13 15:05:11 UTC

This is fixed by this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1573965

Comment 6 Dan Trainor 2018-06-19 17:54:29 UTC

Verified this works without error according to the steps specified when the bz was opened.

Also, note the bug referenced in this bug[0], which was supposed to fix this bug, was also VERIFIED yesterday.

---

[0] https://bugzilla.redhat.com/show_bug.cgi?id=1573965

Comment 8 errata-xmlrpc 2018-06-27 13:57:12 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/RHEA-2018:2086