Bug 2217725
| Summary: | [RHOSP 17.0] When specifying OS_PROJECT_NAME in the rc file variables the command fails to execute. | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Takemi Asakura <tasakura> |
| Component: | python-openstackclient | Assignee: | OSP Team <rhos-maint> |
| Status: | CLOSED NOTABUG | QA Contact: | Nobody <nobody> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17.0 (Wallaby) | CC: | apevec, jpichon, lhh, tkajinam |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-06-28 01:55:32 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: | |||
|
Description
Takemi Asakura
2023-06-27 03:06:28 UTC
Did you try removing OS_CLOUD fro your customized rc file? The described example contains OS_CLOUD=overcloud, and that means you are loading the information in cloud config. We intentionally kept both OS_CLOUD and individual environment parameters to allow legacy clients to load these parameters but we don't support mixing up different credential by OS_CLOUD and OS_<foo>. Hello Takashi, Thank you for your prompt response! I can confirm that the command executed successfully when I commented `export OS_CLOUD=overcloud`. Now I understand setting `export OS_CLOUD=overcloud` loads the clouds.yaml file[1]. Upon examining the contents of clouds.yaml, I discovered that the overcloud configuration is loading the admin project[2]. I created the rc file from overcloudrc, but until RHOSP 17.0.0, we used `OS_CLOUDNAME` instead of `OS_CLOUD`. Was `OS_CLOUDNAME` merely specifying the name of the cloud without loading clouds.yaml? Best regards, -- Takemi Asakura Technical Support Engineer, OpenStack Tokyo, Japan [1] https://docs.openstack.org/python-openstackclient/wallaby/cli/man/openstack.html#environment-variables ~~~ OS_CLOUD The name of a cloud configuration in clouds.yaml. ~~~ [2] ~~~ [stack@undercloud-0 ~]$ cat ~/.config/openstack/clouds.yaml clouds: heat: auth_type: none endpoint: http://127.0.0.1:8006/v1/admin overcloud: auth: auth_url: http://10.0.0.131:5000 password: **** project_domain_name: Default project_name: admin user_domain_name: Default username: admin cacert: '' identity_api_version: '3' region_name: regionOne volume_api_version: '3' undercloud: auth: auth_url: https://192.168.24.2:13000 password: **** project_domain_name: Default project_name: admin user_domain_name: Default username: admin cacert: /etc/pki/ca-trust/source/anchors/cm-local-ca.pem identity_api_version: '3' region_name: regionOne volume_api_version: '3' ~~~ (In reply to Takemi Asakura from comment #2) ... > I created the rc file from overcloudrc, but until RHOSP 17.0.0, we used > `OS_CLOUDNAME` > instead of `OS_CLOUD`. Was `OS_CLOUDNAME` merely specifying the name of the > cloud without > loading clouds.yaml? You are correct. OS_CLOUDNAME was used to determine the PS1 and is not used by openstackclient. If OS_CLOUD was causing the problem then we can probably just close this as NOTABUG because it's "reasonable" that mixing up two credentials in two formats breaks the discovery. Hello Takashi, Thank you for your response. I have understood the functionality of OS_CLOUD and OS_CLOUDNAME with openstackclient. The issue was caused by loading clouds.yaml with OS_CLOUD, so please close it as NOTABUG. Thank you, Takemi |