58b99bf5ee
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 |
||
---|---|---|
.. | ||
cinder-api-container-puppet.yaml | ||
cinder-backend-dellemc-unity-puppet.yaml | ||
cinder-backend-dellemc-vmax-iscsi-puppet.yaml | ||
cinder-backend-dellemc-vnx-puppet.yaml | ||
cinder-backend-dellemc-xtremio-iscsi-puppet.yaml | ||
cinder-backend-dellps-puppet.yaml | ||
cinder-backend-dellsc-puppet.yaml | ||
cinder-backend-netapp-puppet.yaml | ||
cinder-backend-nvmeof-puppet.yaml | ||
cinder-backend-pure-puppet.yaml | ||
cinder-backend-scaleio-puppet.yaml | ||
cinder-backend-veritas-hyperscale-puppet.yaml | ||
cinder-backup-container-puppet.yaml | ||
cinder-backup-pacemaker-puppet.yaml | ||
cinder-base.yaml | ||
cinder-common-container-puppet.yaml | ||
cinder-hpelefthand-iscsi-puppet.yaml | ||
cinder-scheduler-container-puppet.yaml | ||
cinder-volume-container-puppet.yaml | ||
cinder-volume-pacemaker-puppet.yaml |