openstack team mailing list archive

["Vaze, Mandar" <Mandar.Vaze@xxxxxxxxxxx>]

In my setup, I have SERVICE_TOKEN defined in localrc, which is used by stack.sh (via read_password function) to set the environment variable, eventually to be used by keystone_data.sh  (But probably you know all that) and I don't see the error. (But I somehow still have prettytable 0.5 - so my guess given below - which may be incorrect and/or confusing - sorry about that)

Re "What I can't figure out is what changed in the last couple days" - I am not sure :(

-Mandar

From: Gabriel Hurley [mailto:Gabriel.Hurley@xxxxxxxxxx]
Sent: Friday, June 29, 2012 2:02 AM
To: Ke Wu; Vaze, Mandar
Cc: openstack mail list
Subject: RE: [Openstack] [Devstack]Keystone authentication problem when installing

I'm seeing this error too. It appears that the environment variables (SERVICE_TOKEN, etc.) aren't getting exported, causing keystoneclient to not find them in the environment and triggering that error.

What I can't figure out is what changed in the last couple days to make this suddenly stop working. :-/ I'm still looking into it on my end, but any other ideas would be helpful.


-          Gabriel

From: openstack-bounces+gabriel.hurley=nebula.com@xxxxxxxxxxxxxxxxxxx<mailto:openstack-bounces+gabriel.hurley=nebula.com@xxxxxxxxxxxxxxxxxxx> [mailto:openstack-bounces+gabriel.hurley=nebula.com@xxxxxxxxxxxxxxxxxxx]<mailto:[mailto:openstack-bounces+gabriel.hurley=nebula.com@xxxxxxxxxxxxxxxxxxx]> On Behalf Of Ke Wu
Sent: Thursday, June 28, 2012 10:28 AM
To: Vaze, Mandar
Cc: openstack mail list
Subject: Re: [Openstack] [Devstack]Keystone authentication problem when installing

Thanks Mandar,

Yet could you please explain it in detail? I am pretty new to devstack and didn't see the relationship between the bugs you mentioned and the error I encountered.

Appreciate it!

-K

On Jun 27, 2012, at 9:27 PM, Vaze, Mandar wrote:

May be related to https://bugs.launchpad.net/keystone/+bug/995976
Check last comment at https://bugs.launchpad.net/keystone/+bug/995811

-Mandar

From: openstack-bounces+mandar.vaze=nttdata.com@xxxxxxxxxxxxxxxxxxx<mailto:openstack-bounces+mandar.vaze=nttdata.com@xxxxxxxxxxxxxxxxxxx> [mailto:openstack-bounces+mandar.vaze=nttdata.com@xxxxxxxxxxxxxxxxxxx<mailto:nttdata.com@xxxxxxxxxxxxxxxxxxx>] On Behalf Of Ke Wu
Sent: Thursday, June 28, 2012 7:01 AM
To: openstack mail list
Subject: [Openstack] [Devstack]Keystone authentication problem when installing

Hi,

I can't find a mailing list of devstack so I choose to ask here, hope this doesn't spam you guys.

I was trying to build Devstack on my VM (Ubuntu 12.04 server) to start a new environment for Horizon development.

Everything went well until it hit the point to start Keystone service, the error msg was:

Expecting authentication method via
  either a service token, --token or env[SERVICE_TOKEN],
  or credentials, --os_username or env[OS_USERNAME].
+ NOVA_USER_ID=
++ get_field 1
++ read data
++ grep ' service '
++ keystone tenant-list
Expecting authentication method via
  either a service token, --token or env[SERVICE_TOKEN],
  or credentials, --os_username or env[OS_USERNAME].
+ NOVA_TENANT_ID=
++ keystone ec2-credentials-create --user --tenant_id
usage: keystone ec2-credentials-create [--user_id <user-id>]
                                       [--tenant_id <tenant-id>]
keystone ec2-credentials-create: error: argument --user_id: expected one argument
+ CREDS=
++ failed
++ local r=2
++ set +o xtrace

Anybody has an idea why this happened?

Thanks!

-Ke Wu

______________________________________________________________________
Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding


______________________________________________________________________
Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data.  If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding