Description of problem: The `openstack overcloud deploy --stack-only` command will only update the Heat stack. It does NOT update the config-download playbooks. Running the `openstack overcloud deploy --config-download-only` command will run the deployment using the config-download Ansible content that was generated based on the last Heat stack (not the current one). Version-Release number of selected component (if applicable): All RHOSP releases How reproducible: 100% Steps to Reproduce: 1. Update a TripleO Heat template parameter 2. `openstack overcloud deploy --stack-only` 3. `openstack overcloud deploy --config-download-only` Actual results: The updated Heat stack is not used to generate new Ansible content. Expected results: The new Heat parameters should be picked up and used for the config-download run.
This feature should also be extended to include `openstack overcloud config download`.
Or rather, `openstack overcloud deploy --stack-only` should generate the Ansible deployment content.
Also note that given that `openstack overcloud deploy --stack-only` should generate the Ansible deployment content, having both that and `openstack overcloud config download` looks redundant. Those two should be merged into a single command.
An implementation of this RFE has been submitted upstream - linked here [0]. This change implements a new option called `setup-only` which allows the user to omit the `stack-only` flag. This change implements the setup automation required to allow the deployer to run ansible-playbook directly. [0] https://review.opendev.org/c/openstack/python-tripleoclient/+/772701
Moving to osp-17 since patch still open upstream, and we're too close to the deadlines for 16.2.
Test cases pass and automation is in place.
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