-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.14
-
None
-
No
-
False
-
Description of problem:
controller-manager image pre-puller blocks upgrades in environments where the images have already been pulled but the registry server is not available.
Steps to Reproduce:
1. Create a cluster
2.
oc --insecure-skip-tls-verify get deployment -A -o=jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.spec.template.spec.containers[*].imagePullPolicy}{"\n"}{end}' | grep Always catchpointsynthetics-ansible-operator-controller-manager IfNotPresent Always cert-manager-operator-controller-manager IfNotPresent Always nmstate-cert-manager Always nmstate-console-plugin Always nmstate-operator Always nmstate-webhook Always paas-ingress-canary Always aws-s3-provisioner Always
Expected results:
image should be pulled if not exist
the result is expected because of https://github.com/openshift/enhancements/blob/master/enhancements/update/dont-require-registry-during-reboot-and-upgrade.md#dont-use-the-always-pull-policy