From 1fd3ef688ca134a3922f681adcf5389579c8ff03 Mon Sep 17 00:00:00 2001 From: Sofer Athlan-Guyot Date: Thu, 29 Apr 2021 09:57:12 +0200 Subject: [PATCH] Make sure the container configuration is refreshed during update. Following the refactor from Idf004f7a13544dfc1a8a6da033debd1a4f8b96e7 the operations needed to get the container configuration where removed from the step1 file. We need to re-include them explicitly during update so that new changes get taken into account. In the deployment we have this sequence (keeping only those common with update): - step-0 - host-prep-task - common container setup - common deploy steps tasks 1-5 We mimic this sequence in update by placing common container setup before the common deploy steps tasks 1-5. Change-Id: I5df88cf9d84f5fecb50b0c602b7923027d5f12b0 Closes-Bug: 1926281 --- common/deploy-steps.j2 | 2 ++ 1 file changed, 2 insertions(+) diff --git a/common/deploy-steps.j2 b/common/deploy-steps.j2 index 68494fb511..07683e7d3d 100644 --- a/common/deploy-steps.j2 +++ b/common/deploy-steps.j2 @@ -972,6 +972,8 @@ outputs: - import_tasks: deploy_steps_tasks_step_0.yaml vars: step: 0 + - name: Make sure container configuration is refreshed + import_tasks: common_container_setup_tasks.yaml - name: Write config data at the start of step 1 import_tasks: common_deploy_steps_tasks_step_1.yaml {%- for step in range(1,deploy_steps_max) %}