deployment_status.yaml swift object does not exist when plan is created

[Jiri Tomasek]

Currently, the <planName>-messages/deployment_status.yaml swift object is created when deploy_plan workflow is started, this means that until then, client is not able to determine deployment status unless it considers non-existence of that object as 'UNDEPLOYED' deployment status.

This should be improved and we should explicitly set deployment status when deployment plan is created - message sent from create_deployment_plan workflow should set include deployment_status: UNDEPLOYED

Note that when plan creation fails, the object should not be created (deployment status should not be updated) but message should still get sent

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/569418
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=6ffbf62d926e49835f33390dcf1e31ffe7a1a091
Submitter: Zuul
Branch: master

commit 6ffbf62d926e49835f33390dcf1e31ffe7a1a091
Author: Honza Pokorny <email address hidden>
Date: Fri May 18 11:17:47 2018 -0300

    Set deployment status to UNDEPLOYED on plan creation

    Change-Id: Ie2965c4d4d9c84b4cd392d0033ee960fc19ada11
    Closes-Bug: 1771610

[OpenStack Infra (hudson-openstack)]

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