Bug 1223993

Summary: overcloud failure with "openstack Authorization Failed: Cannot authenticate without an auth_url"
Product: [Community] RDO Reporter: Steve Reichard <sreichar>
Component: rdo-managerAssignee: Jiri Stransky <jstransk>
Status: CLOSED EOL QA Contact: Shai Revivo <srevivo>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: JunoCC: bnemec, hbrock, jguiditt, markmc, mburns, sreichar
Target Milestone: ---Keywords: Field
Target Release: Kilo   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-19 15:52:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
output from overcloud redeploy none

Description Steve Reichard 2015-05-21 22:53:29 UTC 
Created attachment 1028454 [details]
output from overcloud redeploy

Description of problem:


Several attempts to deploy on bare metal (dell blades) have failed with an authentication failure.  Partial output is below.  I've scripted the steps as I understand them and have output from all steps.  There scripts, files, and output will be attached.


> Warning: Permanently added '192.0.2.11' (ECDSA) to the list of known hosts.
> The following cert files already exist, use --rebuild to remove the existing files before regenerating:
> /etc/keystone/ssl/certs/ca.pem already exists
> /etc/keystone/ssl/private/signing_key.pem already exists
> /etc/keystone/ssl/certs/signing_cert.pem already exists
> Connection to 192.0.2.11 closed.
> PKI initialization in init-keystone is deprecated and will be removed.
> + REGISTER_SERVICE_OPTS=
> + openstack role create swiftoperator
> ERROR: openstack Authorization Failed: Cannot authenticate without an auth_url
> [stack@ospha-inst ~]$ 


Looking at the overcloudrc, it is not right:

> [stack@ospha-inst ~]$ cat overcloudrc 
> export NOVA_VERSION=1.1
> export COMPUTE_API_VERSION=1.1
> export OS_PASSWORD=
> export OS_AUTH_URL=
> export OS_USERNAME=admin
> export OS_TENANT_NAME=admin
> export OS_NO_CACHE=True
> export OS_CLOUDNAME=overcloud
> export no_proxy=,192.0.2.6,192.0.2.11
> [stack@ospha-inst ~]$ 

Version-Release number of selected component (if applicable):

[stack@ospha-inst ~]$ uname -a
Linux ospha-inst.cloud.lab.eng.bos.redhat.com 3.10.0-229.4.2.el7.x86_64 #1 SMP Fri Apr 24 15:26:38 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux
[stack@ospha-inst ~]$ cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.1 (Maipo)
[stack@ospha-inst ~]$ rpm -qa | grep -e instack -e rdo
rdo-release-kilo-1.noarch
instack-0.0.6-1.el7ost.noarch
python-rdomanager-oscplugin-0.0.7-dev10.el7.centos.noarch
instack-undercloud-2.1.1-dev14.el7.centos.noarch
rubygem-rdoc-4.0.0-24.el7.noarch
[stack@ospha-inst ~]$ 




How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Steve Reichard 2015-05-21 22:57:13 UTC 
Comment on attachment 1028454 [details]
output from overcloud redeploy

will make link
Comment 3 Ben Nemec 2015-05-29 19:26:42 UTC 
jq: instackenv.json: No such file or directory

My guess is that your env file is named something other than instackenv.json.  The easiest fix is just to rename it to instackenv.json, but you can also set the NODES_JSON env var to the alternate filename.

Hopefully this will be addressed by the unified CLI formalizing the interface rather than relying on magic env vars.
Comment 4 chris alfonso 2015-06-01 18:44:11 UTC 
IIRC, you were able to get further with this with the file naming, is that right?
Comment 5 Steve Reichard 2015-06-03 12:53:01 UTC 
After naming the file as listed, setting the ENV variable and explicitiy passing the file, I was able to get past this
Comment 6 Mark McLoughlin 2015-06-04 11:02:23 UTC 
Sounds like this bug could be closed as NOTABUG, but we should a bug to track this:

> Hopefully this will be addressed by the unified CLI formalizing the interface 
> rather than relying on magic env vars.
Comment 8 Chandan Kumar 2016-05-19 15:52:09 UTC 
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.