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.
Reviewed: https:/ /review. opendev. org/664277 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=df3b4b3c572 4d0736227e3dc13 6dd6f797b02678
Committed: https:/
Submitter: Zuul
Branch: master
commit df3b4b3c5724d07 36227e3dc136dd6 f797b02678
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
Partial-Bug: #1831690