Hide Forgot
Description of problem: After openshift cluster is setup, initial container creation fails for 'default' project. Image pulling seems to be failing. # oc get pods NAME READY STATUS RESTARTS AGE docker-registry-2-deploy 0/1 ContainerCreating 0 18m registry-console-1-deploy 0/1 ContainerCreating 0 18m router-1-deploy 0/1 ContainerCreating 0 18m # oc describe pods/docker-registry-2-deploy Events: FirstSeen LastSeen Count From SubobjectPath Type Reason Message --------- -------- ----- ---- ------------- -------- ------ ------- 27m 27m 1 {default-scheduler } Normal Scheduled Successfully assigned docker-registry-2-deploy to dhcp47-107.lab.eng.blr.redhat.com 26m 4m 9 {kubelet dhcp47-107.lab.eng.blr.redhat.com} Warning FailedSync Error syncing pod, skipping: failed to "StartContainer" for "POD" with ErrImagePull: "Error: image openshift3/ose-pod not found" 26m 10s 108 {kubelet dhcp47-107.lab.eng.blr.redhat.com} Warning FailedSync Error syncing pod, skipping: failed to "StartContainer" for "POD" with ImagePullBackOff: "Back-off pulling image \"openshift3/ose-pod:v3.4.0.13\"" Version-Release number of selected component (if applicable): atomic-openshift-3.4.0.13-1.git.0.406f649.el7.x86_64 How reproducible: 2/2 Steps to Reproduce: 1. setup openshift using 'atomic-openshift-installer install' 2. check if all initial pods are spawn correctly Actual results: None of the initial pods are setup Expected results: setup should complete successfully Additional info: Logs shall be attached shortly.
Closing as this looks like just missing configuration of internal registries for unreleased 3.4 images. Please reopen if I've missed anything, or let us know if you need more info.