From 848569c3fdda1eb26c857c1d593a5a2bbd843015 Mon Sep 17 00:00:00 2001 From: Jose Luis Franco Arza Date: Wed, 30 Sep 2020 10:35:14 +0200 Subject: [PATCH] [Train-only] Configure podman registries during a minor update. If a new insecure registry would be added in the update prepare this wouldn't be included in the Podman's unsecure registries configuration. Leading to a failed update as the overcloud nodes wouldn't be able to reach the insecure registry. Reusing the upgrade_taks that took care of configuring the insecure registries, as well as adding (if it wasn't already) the underclouds hostname in /etc/hosts. In theory, these tasks should be idempotent. So, if all these configurations are already done the tasks should not do anything. Change-Id: I8a73fd31ac365146439191111bacfb4b6c5b9ba3 --- deployment/podman/podman-baremetal-ansible.yaml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/deployment/podman/podman-baremetal-ansible.yaml b/deployment/podman/podman-baremetal-ansible.yaml index 3873d6bfb0..f9bb5ff463 100644 --- a/deployment/podman/podman-baremetal-ansible.yaml +++ b/deployment/podman/podman-baremetal-ansible.yaml @@ -160,7 +160,7 @@ outputs: - name: Run podman install when: - step|int == 1 - block: + block: &podman_configure_registry # This is needed when moving from Docker to Podman. The SELinux context # is wrong for podman, especially if the directory was created by # docker itself. @@ -223,6 +223,11 @@ outputs: - never - system_upgrade - system_upgrade_prepare + update_tasks: + - name: Run podman registry configuration + when: + - step|int == 1 + block: *podman_configure_registry post_upgrade_tasks: - name: Purge everything about docker on the host