Fix update of non HA container during update.
After the refactoring of step_1 to improve speed during deployment, we were not updating the /var/lib/container-puppet/container-puppet.json or the container-startup-configs.json for instance. Net result is that the configuration is being done on the initially deployed container and non HA container are not updated. Note that not all step1 tasks were refarctored into the deploy_steps_tasks_step_1. So we still need to loop over step 1 in the deploy_steps_tasks. Closes-Bug: #1848359 Change-Id: I76b16cd7781ea601778004afa4e0bc3020ce3c59
This commit is contained in:
parent
bf60423c0f
commit
6e649ccc7e
@ -955,6 +955,7 @@ outputs:
|
|||||||
loop_var: step
|
loop_var: step
|
||||||
- import_tasks: {{role.name}}/host_prep_tasks.yaml
|
- import_tasks: {{role.name}}/host_prep_tasks.yaml
|
||||||
when: tripleo_role_name == '{{role.name}}'
|
when: tripleo_role_name == '{{role.name}}'
|
||||||
|
- import_tasks: common_deploy_steps_tasks_step_1.yaml
|
||||||
- include_tasks: common_deploy_steps_tasks.yaml
|
- include_tasks: common_deploy_steps_tasks.yaml
|
||||||
with_sequence: start=1 end={{deploy_steps_max-1}}
|
with_sequence: start=1 end={{deploy_steps_max-1}}
|
||||||
loop_control:
|
loop_control:
|
||||||
|
Loading…
Reference in New Issue
Block a user