Keystone command failure after SQL backend changes

[Gabriel Hurley]

The Keystone SQL backend changes altered the code here:

https://github.com/openstack-dev/devstack/commit/3f7c06f5aaff5d3e2ec28931e0fe4ab8376208e6#L1L1944

And subsequently forgot to pass the auth parameters into the new keystone commands, causing the following error:

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

This only happens with swift enabled, since the offending code is in a conditional block.

[Dean Troyer (dtroyer)]

Fixed in https://review.openstack.org/#/c/9147/ by properly setting up the OS_* environment variables after keystone is initialized.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/9147
Committed: http://github.com/openstack-dev/devstack/commit/5cc2129c4b160b3d03c5514abc9cda1ca263071c
Submitter: Jenkins
Branch: master

commit 5cc2129c4b160b3d03c5514abc9cda1ca263071c
Author: Dean Troyer <email address hidden>
Date: Thu Jun 28 17:50:28 2012 -0500

    Fix keystone auth failures

    Set up environment credentials after keystone is initialized

    Fixes bug 1019056

    Change-Id: Ifd0080f102e08c1f5517a08681ac277709f191c0