Bug 1364220

Summary:	Skipping "horizon" postconfig with latest openstack-tripleo-heat-templates
Product:	Red Hat OpenStack	Reporter:	Mike Orazi <morazi>
Component:	python-tripleoclient	Assignee:	Jiri Stransky <jstransk>
Status:	CLOSED ERRATA	QA Contact:	Ido Ovadia <iovadia>
Severity:	high	Docs Contact:
Priority:	high
Version:	9.0 (Mitaka)	CC:	achernet, akaris, aludwar, apannu, arkady_kanevsky, cdevine, christopher_dearborn, cllewellyn, david_paterson, dberry, dmacpher, gael_rehault, hbrock, jcoufal, jjoyce, John_walsh, jslagle, jstransk, jtomasek, kazen, kejones, kurt_hey, mburns, mfuruta, morazi, opavlenk, pmannidi, randy_perryman, rhel-osp-director-maint, royoung, sreichar, tvignaud, vaggarwa, vcojot
Target Milestone:	rc	Keywords:	Triaged
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-tripleoclient-5.0.0-0.20160907170033.b0d7ce7.el7ost	Doc Type:	Bug Fix
Doc Text:	OpenStack Dashboard (horizon) was incorrectly included in list of services the director uses to create endpoints in OpenStack Identity (keystone). A misleading 'Skipping "horizon" postconfig' message appeared when deploying the overcloud. This fix removes horizon from the service list endpoints added to keystone and modifies the "skipping postconfig" messages to only appear in debug mode. The misleading 'Skipping "horizon" postconfig' message no longer appears.	Story Points:	---
Clone Of:	1347063	Environment:
Last Closed:	2016-12-14 15:48:41 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:	1347063
Bug Blocks:	1305654, 1353696

Comment 1 Jiri Stransky 2016-08-16 14:24:15 UTC

Vincent i see you reported the original bug 1347063. Can you please help me understand the impact of this bug -- does it break anything in terms of functionality or is it just a confusing message being printed? On bug 1347063 you mentioned that horizon actually works.

I'm wondering if the right thing to do here is to just stop attempting to create an endpoint for Horizon. I vaguely recall that this endpoint was needed only by the original Tuskar UI but i'm not sure if it's still needed for anything nowadays. Scanning the internets, i couldn't find any mentions of people creating a keystone endpoint for Horizon and using it for anything.

Comment 2 Jiri Stransky 2016-08-16 14:26:49 UTC

Jirka, do you know if TripleO UI needs the overcloud Horizon endpoint for something?

Comment 3 Jiri Tomasek 2016-08-16 14:41:17 UTC

TripleO UI does not currently need overcloud Horizon endpoint. I think it is ok to remove it, especially if such implementation is incomplete and causes bugs.

Comment 4 Vincent S. Cojot 2016-08-16 16:07:56 UTC

Hi Jiri,
Horizon works but the 'horizon' service does not get populated anymore in 'keystone service-list'. I have no idea what uses that part, btw.

Comment 5 Andreas Karis 2016-08-16 16:14:38 UTC

Hello,

If horizon worked, we wouldn't have opened the bug. This is not about the endpoint. Horizon is not accessible without the above workaround.

Comment 6 Andreas Karis 2016-08-16 16:19:54 UTC

(at least my customers couldn't access horizon)

Comment 11 Jiri Stransky 2016-08-18 09:19:56 UTC

Thanks for the info all. Seems like this is not a functional problem but has a potential to generate confusion.

Comment 13 Jiri Stransky 2016-09-19 15:08:50 UTC

Merged, it's on the way to Newton.

Comment 17 Mike Burns 2016-09-29 05:58:52 UTC

*** Bug 1379893 has been marked as a duplicate of this bug. ***

Comment 18 Ido Ovadia 2016-10-06 16:07:40 UTC

Verified
========
python-tripleoclient-5.2.0-1.el7ost.noarch

Comment 22 Radomir Dopieralski 2016-10-20 11:40:13 UTC

*** Bug 1353696 has been marked as a duplicate of this bug. ***

Comment 24 errata-xmlrpc 2016-12-14 15:48:41 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