886c51549f
That step include, in particular, the puppet-container.py/sh creation file plus some other task that should happen very early during the deploy process. During update if a change in puppet-container.py happen in the template we have to trigger those steps to get the changes. This is especially critical because we run puppet container configuration during the update stage. Patch slighly adjusted for the backport as step_1 refactoring doesn't exist in stein and neither does container-puppet.sh. Closes-Bug: #1853156 Change-Id: I26406da82c584dc5093c17ad26f263057a5cbcaa (cherry picked from commit10a523a03d) (cherry picked from commit3c71c99d7c)
11 lines
459 B
YAML
11 lines
459 B
YAML
- name: Create /var/lib/container-puppet
|
|
no_log: True
|
|
file: path=/var/lib/container-puppet state=directory setype=svirt_sandbox_file_t selevel=s0 recurse=true
|
|
- name: Write container-puppet.py
|
|
no_log: True
|
|
copy: src=docker_puppet_script.yaml dest=/var/lib/container-puppet/container-puppet.py force=yes mode=0600
|
|
{%- for role in roles %}
|
|
- import_tasks: {{role.name}}/deploy_steps_tasks.yaml
|
|
when: tripleo_role_name == '{{role.name}}'
|
|
{%- endfor %}
|