[rhos-list] keystone or dashboard problem?

Fri Dec 7 14:02:52 UTC 2012

Thank's for all your answers,
I could fix it!

I created a new tenant named "admin" (don't know if the name is important) and sourced a new file with the OS_* variables after unsetting SERVICE_TOKEN and SERVICE_ENDPOINT.
I didn't know that SERVICE_TOKEN and SERVICE_ENDPOINT are intended to work together. Good to know !
Another question: Is it mandatory to create a specific tenant called "Service" and adding to him a user for each Openstack-Service (nova, glance, ...). It is mentioned in the official guide but not in the RedHat Preview.

Thanks,

Nicolas.

-----Original Message-----
From: Derek Higgins [mailto:derekh at redhat.com] 
Sent: vendredi 7 décembre 2012 14:37
To: Vogel Nicolas
Cc: Fedora Cloud SIG; rhos-list at redhat.com
Subject: Re: [rhos-list] keystone or dashboard problem?

On 12/07/2012 01:26 PM, Matthias Runge wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 12/07/2012 02:16 PM, Vogel Nicolas wrote:
>> 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.
>>
> 
> I've made a file containing something like that:
> export OS_USERNAME=admin
> export OS_PASSWORD=xxxxxxxxxxx
> export OS_TENANT_NAME=admin
> export OS_AUTH_URL=http://127.0.0.1:35357/v2.0/
> 
> Every time, when I'm using keystone (or other OpenStack command line 
> tools), I'm sourcing that file for my session once. But: That is not 
> sourced automatically, I'm doing that by hand.
Hi Nicolas,

I think your original error is displayed if you have one of SERVICE_TOKEN or SERVICE_ENDPOINT in your environment but not both, they are intended to be used together. Also you should use these  or the OS_* environment variables but not both.

Can you make sure you have removed the SERVICE_TOKEN and SERVICE_ENDPOINT variables from your shell environment.

$ unset SERVICE_TOKEN
$ unset SERVICE_ENDPOINT

and that you have defined the 4 OS_ variables that Matthias mentioned

thanks,
Derek.

> 
> That's it.
> 
> Cheers,
> Matthias
>> -----Original Message----- From: rhos-list-bounces at redhat.com 
>> [mailto:rhos-list-bounces at redhat.com] On Behalf Of Matthias Runge
>> Sent: vendredi 7 décembre 2012 10:28 To: rhos-list at 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 at redhat.com 
>>> https://www.redhat.com/mailman/listinfo/rhos-list
>>>
>>
>> _______________________________________________ rhos-list mailing 
>> list rhos-list at redhat.com 
>> https://www.redhat.com/mailman/listinfo/rhos-list
>> _______________________________________________ cloud mailing list 
>> cloud at lists.fedoraproject.org 
>> https://admin.fedoraproject.org/mailman/listinfo/cloud
>>
> 
> 
> - --
> Matthias Runge <mrunge at matthias-runge.de>
>                <mrunge at fedoraproject.org> -----BEGIN PGP 
> SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> Comment: Using GnuPG with undefined - http://www.enigmail.net/
> 
> iQEcBAEBAgAGBQJQwe6PAAoJEOnz8qQwcaIWsNcH/1HA5Id1O2OtakIxGYctpXRT
> p5sUrta57cduHom6K9gUc9KGcQHOb+WmhlNYJ+qmnkVexcGpZjbONwKdcbaLWAa0
> iYoVQTlwBbc6dfo8KojkjYcKTMwQeelWKQVWtTgD4SVlNq2v+zh2lMF46XmR6lD4
> 1s6krFQShuN0KaITU4Lsg38G+ZPDZp8WTs2EwhaONvZmSJoOOt4ej66RLTfzd7AZ
> iqREmvAgIpjGzn2hc147BfpSry9L8fhd4TlIAJqfdiL7pSzeW1iTSz1QxT0h2dwB
> tBW3H3HZzbIaTNWo/5Ra1BfE7/pmkQKwdVPqH18l93lhYERK7/xPDAguek1eDKo=
> =7Qi/
> -----END PGP SIGNATURE-----
> _______________________________________________
> cloud mailing list
> cloud at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/cloud
> 