commit de06f9373aa3f26739deaae7b57901679cf62373
Author: James Slagle <email address hidden>
Date: Tue Oct 16 16:28:15 2018 -0400
Sync state if needed during retrieval
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.
Reviewed: https:/ /review. openstack. org/611168 /git.openstack. org/cgit/ openstack/ tripleo- common/ commit/ ?id=de06f9373aa 3f26739deaae7b5 7901679cf62373
Committed: https:/
Submitter: Zuul
Branch: master
commit de06f9373aa3f26 739deaae7b57901 679cf62373
Author: James Slagle <email address hidden>
Date: Tue Oct 16 16:28:15 2018 -0400
Sync state if needed during retrieval
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: I6d329e974965ed f28d6f5b12e6854 319cfb683f4
Closes-Bug: #1798193