Set DeployIdentifier on update/upgrade/ffwd prepare actions
We have separate actions for deploy vs. upgrade prepare, because on
upgrade prepare we don't want to trigger Ansible. DeployIdentifier was
left out from the upgrade prepare action, which got exposed as a bug
after we fixed --skip-deploy-identifier functionality in
Ibab17dcaeebea65135fca4f40562109c90f36c27.
Over time it would be good to further improve code sharing between
`overcloud deploy` and `overcloud update/upgrade/ffwd prepare`, but
for now we need a backportable fix so we just set DeployIdentifier in
the upgrade prepare action.
Additionally it turned out that we never updated the plan env via the
UpdateStackAction as intended, which is now fixed too.
Reviewed: https:/ /review. openstack. org/619759 /git.openstack. org/cgit/ openstack/ tripleo- common/ commit/ ?id=c907add5128 17363207ba8899a 3cb14e122078d4
Committed: https:/
Submitter: Zuul
Branch: master
commit c907add51281736 3207ba8899a3cb1 4e122078d4
Author: Jiri Stransky <email address hidden>
Date: Fri Nov 23 16:54:10 2018 +0100
Set DeployIdentifier on update/upgrade/ffwd prepare actions
We have separate actions for deploy vs. upgrade prepare, because on deploy- identifier functionality in bea65135fca4f40 562109c90f36c27 .
upgrade prepare we don't want to trigger Ansible. DeployIdentifier was
left out from the upgrade prepare action, which got exposed as a bug
after we fixed --skip-
Ibab17dcaee
Over time it would be good to further improve code sharing between
`overcloud deploy` and `overcloud update/upgrade/ffwd prepare`, but
for now we need a backportable fix so we just set DeployIdentifier in
the upgrade prepare action.
Additionally it turned out that we never updated the plan env via the Action as intended, which is now fixed too.
UpdateStack
Change-Id: Iefaff07995ae47 dcef58739eaf90c 4026fe255b0
Closes-Bug: #1804858