Bug 1689626

Summary:	multi-domain keystone configuration must be reflected in Horizon as well
Product:	Red Hat OpenStack	Reporter:	Amit Ugol <augol>
Component:	python-django-horizon	Assignee:	Radomir Dopieralski <rdopiera>
Status:	CLOSED ERRATA	QA Contact:	Eldar Weiss <eweiss>
Severity:	low	Docs Contact:
Priority:	low
Version:	14.0 (Rocky)	CC:	athomas, jrist, rdopiera
Target Milestone:	beta	Keywords:	Documentation, Triaged
Target Release:	15.0 (Stein)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-django-horizon-15.1.1-0.20190612120427.c3ac75e.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-21 11:20:49 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:	1688685
Bug Blocks:

Description Amit Ugol 2019-03-17 04:12:02 UTC

With multi-domain configuration enabled for the OSP horizon dashboard, the customer experienced a UI crash when logging in as a domain admin.

With multi-domain support enabled horizon incorrectly attempts to grant access to the list domains view within the UI which triggered a crash of the UI due to a logic bug in the error handling of the exception.

Even as the exception was handled in 1688685, if we don't configure the system well, there will be errors and changing configuration on a live system is a hassle.

Comment 4 Eldar Weiss 2019-07-22 12:19:18 UTC

Verified this now on RHOSP15 in my server 10.35.160.195
UI doesn't crash anymore on multiple domains.

Comment 6 errata-xmlrpc 2019-09-21 11:20:49 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-2019:2811