79c687cd32
Update the deployment status if needed when retrieving the status. We do
this since tripleoclient does not yet use a single API for overcloud
deployment. Since there is no long running process to make sure the
status is updated, we instead update the status if needed when we get it
with this action.
The logic to update the status is detailed in a comment in the code.
Also as part of this commit the status is kept as deploying in
deploy_play when not triggering config_download, since the client will
trigger config_download on it's own. It makes more sense to keep the
status as deploying in that scenario.
Change-Id: I6d329e974965edf28d6f5b12e6854319cfb683f4
Closes-Bug: #1798193
(cherry picked from commit
|
||
---|---|---|
.. | ||
access.yaml | ||
baremetal.yaml | ||
ceph-ansible.yaml | ||
deployment.yaml | ||
derive_params_formulas.yaml | ||
derive_params.yaml | ||
fernet-key-rotate.yaml | ||
heat_environments.yaml | ||
messaging.yaml | ||
networks.yaml | ||
octavia_post.yaml | ||
package_update.yaml | ||
parameters.yaml | ||
plan_management.yaml | ||
rename_ceph_ansible_fetch_directory.yaml | ||
scale.yaml | ||
skydive-ansible.yaml | ||
stack.yaml | ||
support.yaml | ||
swift_backup.yaml | ||
swift_ring_rebalance.yaml | ||
swift.yaml | ||
undercloud_backup.yaml | ||
validations.yaml |