Bug 1416911 - rhosp-director: the overcloudrc in osp11 doesn't set the "OS_TENANT_NAME" anymore. Glance needs it.
Summary: rhosp-director: the overcloudrc in osp11 doesn't set the "OS_TENANT_NAME" any...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ga
: 11.0 (Ocata)
Assignee: Angus Thomas
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-26 19:02 UTC by Alexander Chuzhoy
Modified: 2017-03-29 17:31 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-29 17:31:17 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Alexander Chuzhoy 2017-01-26 19:02:42 UTC
rhosp-director: the overcloudrc in osp11 doesn't set the "OS_TENANT_NAME" anymore. Glance needs it.


Environment:
instack-undercloud-6.0.0-0.20170120171137.c891931.el7ost.noarch
python-glance-14.0.0-0.20170121044011.18acc70.el7ost.noarch
python-glanceclient-2.5.0-0.20161111191712.d419632.el7ost.noarch
openstack-glance-14.0.0-0.20170121044011.18acc70.el7ost.noarch


Steps to reproduce:

1. Deploy overcloud
2. source overcloudrc
3. run "glance image-list"

Result:

You must provide a project_id or project_name (with project_domain_name or project_domain_id) via   --os-project-id (env[OS_PROJECT_ID])  --os-project-name (env[OS_PROJECT_NAME]),  --os-project-domain-id (env[OS_PROJECT_DOMAIN_ID])  --os-project-domain-name (env[OS_PROJECT_DOMAIN_NAME])


"openstack image list" works as expected.


Here's the content of overcloudrc:
[stack@instack ~]$ cat overcloudrc
# Clear any old environment that may conflict.
for key in $( set | awk '{FS="="}  /^OS_/ {print $1}' ); do unset $key ; done
export OS_NO_CACHE=True
export OS_CLOUDNAME=overcloud
export OS_AUTH_URL=http://192.168.200.189:5000/v2.0
export NOVA_VERSION=1.1
export COMPUTE_API_VERSION=1.1
export OS_USERNAME=admin
export OS_PASSWORD=w3XvHAUzzdCjjnpbdbWe2vgyu
export no_proxy=,192.168.200.189,192.168.24.6
export OS_PROJECT_NAME=admin
export PYTHONWARNINGS="ignore:Certificate has no, ignore:A true SSLContext object is not available"


Initializing the "OS_TENANT_NAME" var resolves the issue.

Comment 1 Alexander Chuzhoy 2017-03-29 17:30:28 UTC
Environment:
python-glance-store-0.20.1-0.20170210090113.3646e91.el7ost.noarch
puppet-glance-10.3.0-1.el7ost.noarch
openstack-glance-14.0.0-3.el7ost.noarch
instack-undercloud-6.0.0-2.el7ost.noarch
python-glance-14.0.0-3.el7ost.noarch
python-glanceclient-2.6.0-1.el7ost.noarch


Don't reproduce the issue anymore:

[stack@undercloud ~]$ . overcloudrc
[stack@undercloud ~]$ glance image-list
+--------------------------------------+----------------------+
| ID                                   | Name                 |
+--------------------------------------+----------------------+
| 351ecf03-9475-4a6f-93d6-cedbf66f6acd | centos-image         |
| 494ac8e9-db87-4126-aea8-b6d4bcd0e981 | centos-image.initrd  |
| 63b84dd1-b332-4e78-adad-f793632a4e30 | centos-image.vmlinuz |
| a87348ec-d704-41c2-9df1-49208af015ad | cirros               |
| 344f4980-fdb4-4463-89bf-5789215b7f2b | deploy-kernel        |
| 95955bd9-24d9-421f-97a6-1b457464cb21 | deploy-ramdisk       |
| 40befdfa-78c5-44be-ae63-ea89109880cf | rhel-6-9             |
+--------------------------------------+----------------------+
[stack@undercloud ~]$ cat overcloudrc
# Clear any old environment that may conflict.
for key in $( set | awk '{FS="="}  /^OS_/ {print $1}' ); do unset $key ; done
export OS_NO_CACHE=True
export OS_CLOUDNAME=overcloud
export OS_AUTH_URL=http://X.X.X.X:5000/v2.0
export NOVA_VERSION=1.1
export COMPUTE_API_VERSION=1.1
export OS_USERNAME=admin
export OS_PASSWORD=xccJPNbE94MKqwpjbT4H2uGh7
export no_proxy=,X.X.X.X,192.168.0.8
export OS_PROJECT_NAME=admin
export PYTHONWARNINGS="ignore:Certificate has no, ignore:A true SSLContext object is not available"
[stack@undercloud ~]$


Note You need to log in before you can comment on or make changes to this bug.