Hide Forgot
Description of problem: When the pod is created it pulls the image sucessfully but immediately after that it mentions "no such image"error Version-Release number of selected component (if applicable): OSE 3.1.1 How reproducible: Steps to Reproduce: 1. oc describe pod metrics-17-in367 Name: metrics-17-in367 Namespace: dsi-metrics-uat Image(s): 172.17.116.160:5000/dsi-metrics-uat/metrics@sha256:04a08751750595e0590142f404bc7afcd7d988422077c299a5da9dad4211f7fb Node: gbrdsr000003085.intranet.barcapint.com/10.41.11.104 Start Time: Thu, 17 Mar 2016 17:07:00 +0000 Labels: deployment=metrics-17,deploymentconfig=metrics,name=metrics Status: Pending Reason: Message: IP: 10.1.0.31 Replication Controllers: metrics-17 (1/1 replicas created) Containers: metrics: Container ID: Image: 172.17.116.160:5000/dsi-metrics-uat/metrics@sha256:04a08751750595e0590142f404bc7afcd7d988422077c299a5da9dad4211f7fb Image ID: QoS Tier: cpu: BestEffort memory: BestEffort State: Waiting Reason: RunContainerError Ready: False Restart Count: 0 Environment Variables: DSI_METRICS_DOMAIN: INTRANET DSI_METRICS_USER: sysDSIMetricsApp DSI_METRICS_PASSWORD: sG#rzk5B DSI_METRICS_FQ_DOMAIN: INTRANET.BARCAPINT.COM Conditions: Type Status Ready False Volumes: default-token-xnbd3: Type: Secret (a secret that should populate this volume) SecretName: default-token-xnbd3 Events: FirstSeen LastSeen Count From SubobjectPath Reason Message �������� ������� ����� ��� ������������� ������ ������ 2m 2m 1 {scheduler } Scheduled Successfully assigned metrics-17-in367 to gbrdsr000003085.intranet.barcapint.com 2m 2m 1 {kubelet gbrdsr000003085.intranet.barcapint.com} implicitly required container POD Pulled Container image "barclays-registry-pilot.intranet.barcapint.com/openshift3/ose-pod:v3.1.1.6" already present on machine 2m 2m 1 {kubelet gbrdsr000003085.intranet.barcapint.com} implicitly required container POD Created Created with docker id 702ee60188a7 2m 2m 1 {kubelet gbrdsr000003085.intranet.barcapint.com} implicitly required container POD Started Started with docker id 702ee60188a7 2m 2m 1 {kubelet gbrdsr000003085.intranet.barcapint.com} spec.containers{metrics} Pulling pulling image "172.17.116.160:5000/dsi-metrics-uat/metrics@sha256:04a08751750595e0590142f404bc7afcd7d988422077c299a5da9dad4211f7fb" 2m 2m 1 {kubelet gbrdsr000003085.intranet.barcapint.com} spec.containers{metrics} Pulled Successfully pulled image "172.17.116.160:5000/dsi-metrics-uat/metrics@sha256:04a08751750595e0590142f404bc7afcd7d988422077c299a5da9dad4211f7fb" 2m 6s 17 {kubelet gbrdsr000003085.intranet.barcapint.com} spec.containers{metrics} Failed Failed to create docker container with error: no such image 2m 6s 16 {kubelet gbrdsr000003085.intranet.barcapint.com} spec.containers{metrics} Pulled Container image "172.17.116.160:5000/dsi-metrics-uat/metrics@sha256:04a08751750595e0590142f404bc7afcd7d988422077c299a5da9dad4211f7fb" already present on machine 2. Resulting in this state: root@gbrdsr000003085 DEV # oc get pod metrics-17-in367 NAME READY STATUS RESTARTS AGE metrics-17-in367 0/1 RunContainerError 0 5m 3. Actual results: pod results in an error Expected results: It should be successfully create if the image was pulled without any issue. Additional info:
Could we please get the output of `oc get pod metrics-17-in367 -o yaml`? Thanks!
Jhon, I've seen this "no such image" happen occasionally in the Kubernetes CI environment multiple times. See e.g. https://github.com/kubernetes/kubernetes/issues/22166. There's also at least 1 Docker issue: https://github.com/kubernetes/kubernetes/issues/22166. Just wanted to get this on your radar in case you know the root cause.
Is this still an issue?
Closing as not a bug as per irc discussion with Jaspreet.