9bc6640907
The change https://review.opendev.org/#/c/616116 unwinded the swift part of the https://review.opendev.org/#/c/590008/ changes. So the contents of the /var/lib/config-data/swift_ringbuilder config volume used to be managed by container-puppet tool. That made swift containers always restarted because the puppet-generated rings are always changing on each deployment/update execution. Restore that unwinded change back and exclude swift rings from the management of container-puppet tooling. Instead make init containers swift_copy_rings and swift_setup_srv to be always executed (takes the same approach as in https://review.opendev.org/#/c/564798/). That also fixes the issue with swift_copy_rings seems never been executed - at least there is no traces of it in CI jobs logs for swift init containers. Change-Id: I23b469057e4c47c42601beb166f815ee71147c14 Closes-Bug: #1867765 Related-Bug: #1802066 Related-Bug: #1786065 Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com> |
||
|---|---|---|
| .. | ||
| services | ||
| container-puppet.sh | ||
| deploy-steps-playbooks-common.yaml | ||
| deploy-steps-tasks-step-0.j2.yaml | ||
| deploy-steps-tasks-step-1.yaml | ||
| deploy-steps-tasks.yaml | ||
| deploy-steps.j2 | ||
| generate-config-tasks.yaml | ||
| hiera-steps-tasks.yaml | ||
| host-container-puppet-tasks.yaml | ||
| post.j2.yaml | ||