Bug 1632113 - Failed to pull image rpc error: code = 2 desc = unexpected EOF
Summary: Failed to pull image rpc error: code = 2 desc = unexpected EOF
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.6.z
Assignee: Oleg Bulatov
QA Contact: Dongbo Yan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-24 06:47 UTC by rehan
Modified: 2023-09-15 00:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-08 12:38:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description rehan 2018-09-24 06:47:00 UTC
Description of problem:

Issue on pulling image pull on some nodes and image get pulled to most of the nodes successfully even after evacuated, cleared all the docker images and rebooted the node. But the issue still persists.
Version-Release number of selected component (if applicable):

3.6
How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

docker pull 172.xx.xx.xx:5000/paas-jenkins/functest@sha256:7bfe320249bf40091d194a9d432e9b75d01459d66
Trying to pull repository 172.xx.xx.xx:5000/paas-jenkins/functest ...
sha256:7bfe3202761078787d7c2817ae8171149bf40091d194a9d432e9b75d01459d66: Pulling from 172.xx.xx.xx:5000/paas-jenkins/functest
615bc035f9f8: Already exists
1c5fd9dfeaa8: Downloading [==================================================>] 1.216 kB/1.216 kB
51250f44b47f: Downloading [==================================================>] 69.96 MB/69.96 MB
87a6693fe25b: Downloading [==================================================>] 72.91 MB/72.91 MB
ad459ce59895: Downloading [==================================================>] 23.41 kB/23.41 kB
4ce3b6e9abfd: Downloading [==================================================>]    571 B/571 B
unexpected EOF
Expected results:

The Image should be pulled without any error 
Additional info:

Comment 1 Ben Parees 2018-09-24 13:30:13 UTC
Does it consistently fail on the same nodes and consistently work on the same nodes?

We will need the registry logs from all your registry pods, covering a time period during which a pull failed.

Comment 4 Ben Parees 2019-05-08 12:37:36 UTC
See https://bugzilla.redhat.com/show_bug.cgi?id=1632113#c1 for what information we would need to investigate this.

Comment 6 Red Hat Bugzilla 2023-09-15 00:12:34 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days


Note You need to log in before you can comment on or make changes to this bug.