Configure insecure registries before Pacemaker-managed image pulls
Service templates like mysql-pacemaker-puppet.yaml pull fresh
container images in step 2 of the upgrade tasks. In case they come
from an allowed insecure registry, the insecure registries setting
must be in place by step 1. We do just that by reusing the "install
and configure Podman" part of host_prep_tasks.
Change-Id: I36e003c09d7f7768da475d166a20f01347a2934c
Partial-Bug: #1831690
(cherry picked from commit df3b4b3c5724d0736227e3dc136dd6f797b02678)
Reviewed: https:/ /review. opendev. org/667144 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=273f9a32a78 7198904cdb8ca49 71764ba2d53382
Committed: https:/
Submitter: Zuul
Branch: stable/stein
commit 273f9a32a787198 904cdb8ca497176 4ba2d53382
Author: Jiri Stransky <email address hidden>
Date: Mon Jun 10 14:14:33 2019 +0200
Configure insecure registries before Pacemaker-managed image pulls
Service templates like mysql-pacemaker -puppet. yaml pull fresh
container images in step 2 of the upgrade tasks. In case they come
from an allowed insecure registry, the insecure registries setting
must be in place by step 1. We do just that by reusing the "install
and configure Podman" part of host_prep_tasks.
Change-Id: I36e003c09d7f77 68da475d166a20f 01347a2934c 36227e3dc136dd6 f797b02678)
Partial-Bug: #1831690
(cherry picked from commit df3b4b3c5724d07