diff options
| author |   James Slagle <jslagle@redhat.com> | 2017-01-08 11:07:13 -0500 |
|---|---|---|
| committer | James Slagle <jslagle@redhat.com> | 2017-01-08 11:07:13 -0500 |
| commit | 64eb5a1944332301900df1dc4fc2d226336d1bca (patch) | |
| tree | 282491fb300502f38254370fa223b21ceddab6bd /extraconfig/all_nodes/swap.j2.yaml | |
| parent | 10044ba2afe6e33ca22ef656ec298203a485b550 (diff) | |
Add UpgradeInitCommand to deployed-server
The commands specified by UpgradeInitCommand need to be run before
InstanceIdDeployment in deployed-server.yaml, otherwise the upgrades
hang with the resource in progress. This is because the new
python-heat-agent-apply-config has not yet been installed on the
deployed server.
Adding the UpgradeInitCommand (and corresponding
SoftwareConfig/SoftwareDeployment to apply it) will cause the new repos
and python-heat-agent-* rpm's to be installed before
InstanceIdDeployment.
An open question is whether or not Heat should even be triggering the
InstanceIdDepoyment to IN_PROGRESS on upgrade when only the group is
changing from os-apply-config to apply-config. If that turns out to be a
Heat bug, then this patch wouldn't be necessary.
Change-Id: I9d87f995744415b110a7d0bca8d2309d7167148c
Diffstat (limited to 'extraconfig/all_nodes/swap.j2.yaml')
0 files changed, 0 insertions, 0 deletions