Hide Forgot
Description of problem: federation-controller-manager needs to use imagePullPolicy "IfNotPresent" Version-Release number of selected component (if applicable): kubefed2 version: version.Info{Version:"0.0.6", GitCommit:"de6a0a909418f5ddf2d04d232b0ca55aa9cffb49", GitTreeState:"clean", BuildDate:"2019-03-14T00:43:37Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"} Federation v2 controller-manager version: version.Info{Version:"0.0.6", GitCommit:"de6a0a909418f5ddf2d04d232b0ca55aa9cffb49", GitTreeState:"clean", BuildDate:"2019-03-14T00:43:37Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"} $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-03-15-063749 True False 3h32m Cluster version is 4.0.0-0.nightly-2019-03-15-063749 How reproducible: 100% Steps to Reproduce: 1. install federationv2 control plane with operatorhub 2. check federationv2 control plane pod image pull policy Actual results: $ oc get pod federation-controller-manager-5bf69f77f7-4gw7w -oyaml|grep image: -A 1 image: quay.io/openshift/origin-federation-controller:v4.0.0 imagePullPolicy: Always Expected results: The image pull policy should be "IfNotPresent" Additional info:
Should be fixed in 0.0.7 CSV
Verified with: $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.ci-2019-03-31-223338 True False 91m Cluster version is 4.0.0-0.ci-2019-03-31-223338 Federation v2 controller-manager version: version.Info{Version:"v0.0.7", GitCommit:"3e251608ca5357080b95a0bedc45759652f17d29", GitTreeState:"clean", BuildDate:"2019-03-22T22:30:26Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"linux/amd64"} $ oc get pod federation-controller-manager-7ccc559cdd-rmw2h -n federation-system -ojson|jq .spec.containers[].imagePullPolicy "IfNotPresent"
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0758