Description of problem: An overcloud deploy is performed that includes option --setup-only. The heat stack deploy fails with error: 2022-05-31 18:05:46.033 85522 WARNING tripleoclient.export.utils [-] No data returned to export EndpointMapOverride from.: tripleoclient.exceptions.DeploymentError: No overcloud hosts were found in the current stack. Check the stack name and try again.[00m 2022-05-31 18:05:46.033 85522 WARNING tripleoclient.export.utils [-] No data returned to export ExtraHostFileEntries from.: tripleoclient.exceptions.DeploymentError: No overcloud hosts were found in the current stack. Check the stack name and try again.[00m 2022-05-31 18:05:46.033 85522 WARNING tripleoclient.export.utils [-] No data returned to export GlobalConfigExtraMapData from.: tripleoclient.exceptions.DeploymentError: No overcloud hosts were found in the current stack. Check the stack name and try again.[00m 2022-05-31 18:05:46.034 85522 WARNING tripleoclient.utils.utils [-] File /home/stack/overcloud-deploy/overcloud/config-download/overcloud/group_vars/overcloud.json was not found during export: tripleoclient.exceptions.DeploymentError: No overcloud hosts were found in the current stack. Check the stack name and try again.[00m 2022-05-31 18:05:46.034 85522 WARNING tripleoclient.export.utils [-] No data returned to export AllNodesExtraMapData from.: tripleoclient.exceptions.DeploymentError: No overcloud hosts were found in the current stack. Check the stack name and try again.[00m Version-Release number of selected component (if applicable): RHOS-17.0-RHEL-9-20220526.n.0 How reproducible: Every time Steps to Reproduce: 1. Deploy an overcloud. Include option --setup-only in the deploy command. 2. 3. Actual results: Heat stack deploy fails with error above. Expected results: Heat stack deploy is successful. Additional info:
I think the bug here is that the setup-only switch will fail if the stack isn't created. I think we should work on being able to detect the required stack data and provide a better error for operators. While folks familiar with heat can see we're missing information, at present, the error information is fairly cryptic for operators who may not be so familiar.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2022:6543