tripleo-heat-templates/deployment/haproxy
Jose Luis Franco Arza 58b99bf5ee Do not pull image while tagging pcmk images in upgrade_tasks.
During the upgrad of pacemaker managed services there is
a temporary tagging of the existing container image to the
newly image we are going to upgrade to. The input during this
taggins is the container image id, in contrast to what is
passed during deploy tasks, which is the image name with its
tag. For that reason, we can't pull the image in these cases
otherwise the role will fail as it can't find an image to pull
from a container image id.

Change-Id: I4fdd3a05465fa0318b4ec5c079d59f4dd80fa9f2
Closes-Bug: #1814104
2019-02-07 14:58:30 +01:00
..
haproxy-container-puppet.yaml flatten haproxy service configuration 2019-01-29 12:33:16 -05:00
haproxy-internal-tls-certmonger.j2.yaml flatten haproxy service configuration 2019-01-29 12:33:16 -05:00
haproxy-pacemaker-puppet.yaml Do not pull image while tagging pcmk images in upgrade_tasks. 2019-02-07 14:58:30 +01:00
haproxy-public-tls-certmonger.yaml certmonger: Don't restart haproxy on cert renewal 2019-02-01 08:41:32 +02:00
haproxy-public-tls-inject.yaml flatten haproxy service configuration 2019-01-29 12:33:16 -05:00