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.
Jirka, do you know if TripleO UI needs the overcloud Horizon endpoint for something?
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.
Horizon works but the 'horizon' service does not get populated anymore in 'keystone service-list'. I have no idea what uses that part, btw.
If horizon worked, we wouldn't have opened the bug. This is not about the endpoint. Horizon is not accessible without the above workaround.
(at least my customers couldn't access horizon)
Thanks for the info all. Seems like this is not a functional problem but has a potential to generate confusion.
Merged, it's on the way to Newton.
*** Bug 1379893 has been marked as a duplicate of this bug. ***
*** Bug 1353696 has been marked as a duplicate of this bug. ***
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.