Thanks for your answer,
Did you have any idea why Keystone is "expecting an endpoint provided via either
--endpoint or env[SERVICE_ENDPOINT]"?
When I'm trying the following command: "keystone --os-endpoint
http://10.192.75.242:5000/v2.0 token-get", I get "Configuration error: Client
configured to run without a service catalog. Run the client using --os-auth-url or
OS_AUTH_URL, instead of --os-endpoint or OS_SERVICE_ENDPOINT, for example."
The OS_AUTH_URL is configured in my keystonerc_username file and I sourced it
successfully.
I didn't had this problem when I made the installation with CentOS 6.2. Currently
I'm working with CentOS 6.3.
Thank's for answers and ideas to fix the problem.
Regards,
Nicolas.
-----Original Message-----
From: rhos-list-bounces(a)redhat.com [mailto:rhos-list-bounces@redhat.com] On Behalf Of
Matthias Runge
Sent: vendredi 7 décembre 2012 10:28
To: rhos-list(a)redhat.com
Subject: Re: [rhos-list] keystone or dashboard problem?
On 12/06/2012 11:56 AM, Vogel Nicolas wrote:
Hi,
I've just made a new install with the latest version of the « RedHat
getting started guide with Openstack Folsom » Revision 1.0-2.
I'm using CentOS 6.3 for this install.
After installing Openstack-keystone, I'm unable to perform "keystone
user-list" and "keystone token-get". I have sourced the
keystonerc_username file but the system says "Expecting an endpoint
provided via either --endpoint or env[SERVICE_ENDPOINT]". When I'm
explicitly given the endpoint in the command line, the output is
"Configuration error: Client configured to run without a service
catalog. Run the client using --os-auth-url or OS_AUTH_URL, instead of
--os-endpoint or OS_SERVICE_ENDPOINT, for example."
But the OS_AUTH_URL is configured in my keystonerc_username file so I
don't understand why the system asks for it.
I can then all the installation steps without problems, but after I
given my credentials in the dashboard login page (admin/secret or
username/secret), I got "Internal Server Error".
Is that linked with the first problem from Keystone?
Hi,
speaking for dashboard:
dashboard reads its configuration from keystone, so a working keystone is required to be
able to use horizon.
So, yes, your horizon problems should be directly linked to your keystone issues.
Matthias
I'm searching for more information in logs but currently I found no
answer to my questions.
Thanks for help,
*Nicolas Vogel*
*Institut for Information and Communication Technologies*
*University of Applied Sciences - Western Switzerland*
_______________________________________________
rhos-list mailing list
rhos-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rhos-list
_______________________________________________
rhos-list mailing list
rhos-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rhos-list