Hide Forgot
As part of the recovery and rebuild of a cloud, or deployment of a new cloud form the same undercloud, a new name can be chosen for the cloud. This lead to the overcloudrc file of endpoints to be renamed as well. This caused some confusion. a. Enhance the documentation to indicate that the name of the overcloudrc file is dependent on the cloud name Make sure it is clear that changing cloud name results in a new name for the overcloudrc b. Print out the name of the resulting overcloudrc file at the end of the deployment for the user c. Put a standard prefix on all overcloudrc files so that they are always easily identifable for what they are For example automatically name all overcloud rcfiles ‘overcloud<stackname if not ‘overcloud’>rc. Existing resources: https://access.redhat.com/solutions/2709791 After openstack overcloud deploy of an overcloud with a non-default name, cannot find overcloudrc file
So the default stack name is overcloud which results in overcloudrc. It seems that we should just display the generated filename in a summary at the end of the deployment similar to what we do for the undercloud to clear up this configuration.
Upstream this was resolved by outputting the rc file location at the end of a deployment. Is that satisfactory?
According to our records, this should be resolved by python-tripleoclient-9.2.1-12.el7ost. This build is available now.
To the questions in #9, yes this is satisfactory.
Amit, as the QA contact can you provide the QA_Ack?
Michael, this bug requires a PM_ACK.
Verified: openstack-tripleo-common-8.6.6-2.el7ost.noarch python-tripleoclient-9.2.6-2.el7ost.noarch Stack hahaha CREATE_COMPLETE Started Mistral Workflow tripleo.deployment.v1.get_horizon_url. Execution ID: b5e3eba3-27fb-4ace-aabc-0f6b9fd09ea6 Overcloud Endpoint: https://10.0.0.101:13000/ Overcloud Horizon Dashboard URL: https://10.0.0.101:443/dashboard Overcloud rc file: /home/stack/hahaharc Overcloud Deployed