← Back to team overview

openstack team mailing list archive

Re: Error in Horizon or misconfiguration?

 

On 09/18/2012 06:24 PM, Gui Maluf wrote:
Are you using keystone catalog ? check if api-paste keystone configs
are correct.

check if nova-api is running. check if endpoint is correctly created
with # keystone endpoint-list

I don't have any other clue. :/

Gui,

Thank you for your hints!

nova-api is running and keystone lists also configured endpoints. In fact, I didn't experience other issues during my tests using OpenStacks command line tools.

Matthias
On Tue, Sep 18, 2012 at 9:21 AM, Matthias Runge
<mrunge@xxxxxxxxxxxxxxxxx> wrote:
Hi,

currently, I'm testing horizon-rc1.
I'm logged in as admin, and click on any link in the project tab, e.g. on
"Overview" calling the url http://localhost/dashboard/nova/

Then I'm getting an error in http-error-log:

[Tue Sep 18 12:16:37 2012] [error] unable to retrieve service catalog with
token
[Tue Sep 18 12:16:37 2012] [error] Traceback (most recent call last):
[Tue Sep 18 12:16:37 2012] [error]   File
"/usr/lib/python2.7/site-packages/keystoneclient/v2_0/client.py", line 132,
in _extract_service_catalog
[Tue Sep 18 12:16:37 2012] [error]     endpoint_type='adminURL')
[Tue Sep 18 12:16:37 2012] [error]   File
"/usr/lib/python2.7/site-packages/keystoneclient/service_catalog.py", line
62, in url_for
[Tue Sep 18 12:16:37 2012] [error]     raise
exceptions.EndpointNotFound('Endpoint not found.')
[Tue Sep 18 12:16:37 2012] [error] EndpointNotFound: Endpoint not found.

By chance, has anybody a clue, what went wrong or how to debug this further?
There's no error in keystones logs. Keystone answers and does not report an
error.

Thanks,
Matthias
--
Matthias Runge <mrunge@xxxxxxxxxxxxxxxxx>
                <mrunge@xxxxxxxxxxxxxxxxx>

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp





--
Matthias Runge <mrunge@xxxxxxxxxxxxxxxxx>
               <mrunge@xxxxxxxxxxxxxxxxx>


Follow ups

References