Red Hat Bugzilla – Bug 892320
Endpoint not found error showing up in httpd error.log for Horizon
Last modified: 2013-03-05 13:30:42 EST
Description of problem:
Looking at /var/log/httpd/error.log on the Horizon server, one sees a lot of this snippet:
[Sun Jan 06 10:55:26 2013] [error] unable to retrieve service catalog with token
[Sun Jan 06 10:55:26 2013] [error] Traceback (most recent call last):
[Sun Jan 06 10:55:26 2013] [error] File "/usr/lib/python2.6/site-packages/keystoneclient/v2_0/client.py", line 135, in _extract_service_catalog
[Sun Jan 06 10:55:26 2013] [error] endpoint_type='adminURL')
[Sun Jan 06 10:55:26 2013] [error] File "/usr/lib/python2.6/site-packages/keystoneclient/service_catalog.py", line 73, in url_for
[Sun Jan 06 10:55:26 2013] [error] raise exceptions.EndpointNotFound('Endpoint not found.')
[Sun Jan 06 10:55:26 2013] [error] EndpointNotFound: Endpoint not found.
This happens pretty much on any operation you take in the Horizon interface.
A quick upstream bug search finds:
Which indicates that this was an issue fixed in keystone client 2.0
Our current version of keystoneclient in RHOS is python-keystoneclient-0.1.3.27-1.el6.noarch
I checked exceptions.py and the EmptyCatalog exception doesn't appear to be in our version, so it looks like this patch didn't make it into the Folsom stable branch yet.
So perhaps we need to backport this patch to get rid of the error message, which might be a red herring for users
Upstream patch is here:
How do we test this?
(In reply to comment #2)
> How do we test this?
Answer to self: happens on my environment as well.
Verified NVR: python-keystoneclient-0.2.0-1.el6ost.noarch
1. I Ran sanity test in order to trigger the error mentioned in Comment #0
2. I Checked the logs at /var/log/httpd and I didn't find the error mentioned above
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.