Prevent the deploy workflow doing anything if the Heat stack is in (CREATE|UPDATE)_IN_PROGRESS

[Dougal Matthews]

Doing this would prevent any changes to the plan that would then not be deployed. We can do this by adding a workflow task that verifies the stack status.

We should also consider doing this with the other workflows that touch heat. i.e. node delete.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/396567

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/398959

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/398959
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=7f16d103560bf6d915ac717e9d5b092295bc0eae
Submitter: Jenkins
Branch: master

commit 7f16d103560bf6d915ac717e9d5b092295bc0eae
Author: Dougal Matthews <email address hidden>
Date: Thu Nov 17 11:43:36 2016 +0000

    Only start the deploy if the Heat stack isn't already in progress

    At the moment the deploy command will take a number of steps, including
    updating the plan and setting parameters in Mistral. Then when it gets
    to the deploy, the workflow will fail. This change stops it earlier in
    the process, which will be quicker and cleaner.

    Change-Id: I09e40e3f27b9ba3b0f3dad97cece6afbe28bd6b9
    Partial-Bug: #1640249

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/396567
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=afdf3e94554da5fe241256c7ffdf71a4b8eec336
Submitter: Jenkins
Branch: master

commit afdf3e94554da5fe241256c7ffdf71a4b8eec336
Author: Dougal Matthews <email address hidden>
Date: Fri Nov 11 09:56:36 2016 +0000

    Only start the deploy if the Heat stack isn't already in progress

    Closes-Bug: #1640249
    Change-Id: I03a2945e39ba9d6bb3067483acbc746149a3991b

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-common 5.8.0 release.