Red Hat Bugzilla – Bug 1426534
Failed to deploy logging pod via "oc cluster up"
Last modified: 2017-07-24 10:11 EDT
Description of problem: Failed to deploy logging pod via "oc cluster up" Version-Release number of selected component (if applicable): oc v3.5.0.33 kubernetes v1.5.2+43a9be4 features: Basic-Auth GSSAPI Kerberos SPNEGO How reproducible: Always Steps to Reproduce: 1.Create openshift cluster with metrics and logging via "oc cluster up" $ sudo oc cluster up --image=registry.access.redhat.com/openshift3/ose --version=v3.4 --metrics=true --logging=true 2.Wait cluster up, check logging pod $ sudo oc get pod -n logging 3. Actual results: $ sudo oc get all -n logging NAME READY STATUS RESTARTS AGE po/logging-deployer-0clye 0/1 ImagePullBackOff 0 4m Expected results: logging pod is running Additional info: $ sudo oc get event -n logging LASTSEEN FIRSTSEEN COUNT NAME KIND SUBOBJECT TYPE REASON SOURCE MESSAGE 5m 5m 5 logging-deployer-0clye Pod Warning FailedScheduling {default-scheduler } no nodes available to schedule pods 5m 5m 1 logging-deployer-0clye Pod Normal Scheduled {default-scheduler } Successfully assigned logging-deployer-0clye to 10.66.131.231 1m 5m 5 logging-deployer-0clye Pod spec.containers{deployer} Normal Pulling {kubelet 10.66.131.231} pulling image "registry.access.redhat.com/openshift3/ose-logging-deployment:v3.4" 1m 5m 5 logging-deployer-0clye Pod spec.containers{deployer} Warning Failed {kubelet 10.66.131.231} Failed to pull image "registry.access.redhat.com/openshift3/ose-logging-deployment:v3.4": image pull failed for registry.access.redhat.com/openshift3/ose-logging-deployment:v3.4, this may be because there are no credentials on this request. details: (Error response from daemon: {"message":"unknown: Not Found"}) 1m 5m 5 logging-deployer-0clye Pod Warning FailedSync {kubelet 10.66.131.231} Error syncing pod, skipping: failed to "StartContainer" for "deployer" with ErrImagePull: "image pull failed for registry.access.redhat.com/openshift3/ose-logging-deployment:v3.4, this may be because there are no credentials on this request. details: (Error response from daemon: {\"message\":\"unknown: Not Found\"})" 3s 5m 17 logging-deployer-0clye Pod spec.containers{deployer} Normal BackOff {kubelet 10.66.131.231} Back-off pulling image "registry.access.redhat.com/openshift3/ose-logging-deployment:v3.4" 3s 5m 17 logging-deployer-0clye Pod Warning FailedSync {kubelet 10.66.131.231} Error syncing pod, skipping: failed to "StartContainer" for "deployer" with ImagePullBackOff: "Back-off pulling image \"registry.access.redhat.com/openshift3/ose-logging-deployment:v3.4\""
Troy, are we going to tag logging deployer images for v3.4 with the ose- prefix? Or is that only in 3.5?
All 3.2, 3.3, and 3.4 logging and metrics images have both openshift3/ose-{logging,metrics}-<name> and openshift3/{logging,metrics}-<name> The problem with this bug is that you are trying to pull down openshift3/ose-logging-deployment instead of openshift3/ose-logging-deployer It has been logging-deployer since OCP 3.3
Fix merged in origin with PR https://github.com/openshift/origin/pull/13151
Actually needs a 1.5 backport ... PR submitted: https://github.com/openshift/origin/pull/13165 1.4 backport: https://github.com/openshift/origin/pull/13166
1.5 Backport has merged https://github.com/openshift/origin/pull/13165
This has been merged into ocp and is in OCP v3.5.0.38 or newer.
Verified oc version oc v3.5.0.39 kubernetes v1.5.2+43a9be4 $ sudo oc cluster up --image=registry.access.redhat.com/openshift3/ose --version=v3.4 --metrics=true --logging=true could deploy logging pod successfully $ sudo oc get pod -n logging NAME READY STATUS RESTARTS AGE logging-curator-1-z1435 1/1 Running 0 8m logging-deployer-qz4ef 0/1 Completed 0 8m logging-es-83jmlwhp-1-thcp3 1/1 Running 0 8m logging-fluentd-rxx2r 1/1 Running 0 8m logging-kibana-1-55afe 2/2 Running 0 8m
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-2017:0884