From 7adf15df5c0812a74a1697b930003bc1dcddb127 Mon Sep 17 00:00:00 2001 From: Ian Wienand Date: Wed, 23 Sep 2015 11:56:02 +1000 Subject: [PATCH] Add a debugging userrc after keystone is up As a follow-on to the issues raised by I069f46f95656655ae7ba8f3dd929f47eae594b68, rather than a re-write of create_userrc.sh logic, create a temporary userrc that can be helpful for debugging until we have the whole system bootstrapped Change-Id: I3325acffd259cf7f6f4a153c88037cfe8405ca50 --- stack.sh | 29 +++++++++++++++++++++-------- 1 file changed, 21 insertions(+), 8 deletions(-) diff --git a/stack.sh b/stack.sh index 01668c208b..58a708c497 100755 --- a/stack.sh +++ b/stack.sh @@ -1007,14 +1007,27 @@ if is_service_enabled keystone; then # Begone token auth unset OS_TOKEN OS_URL - # Set up password auth credentials now that Keystone is bootstrapped - export OS_AUTH_URL=$KEYSTONE_AUTH_URI - export OS_USERNAME=admin - export OS_USER_DOMAIN_ID=default - export OS_PASSWORD=$ADMIN_PASSWORD - export OS_PROJECT_NAME=admin - export OS_PROJECT_DOMAIN_ID=default - export OS_REGION_NAME=$REGION_NAME + # Rather than just export these, we write them out to a + # intermediate userrc file that can also be used to debug if + # something goes wrong between here and running + # tools/create_userrc.sh (this script relies on services other + # than keystone being available, so we can't call it right now) + cat > $TOP_DIR/userrc_early <