Bug 1601206

Summary:	Unable to deploy from private Docker Hub image
Product:	OpenShift Container Platform	Reporter:	Patrick Kayongo <pat.kayongo>
Component:	Master	Assignee:	Maciej Szulik <maszulik>
Status:	CLOSED DUPLICATE	QA Contact:	Xingxing Xia <xxia>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	3.9.0	CC:	aos-bugs, jokerman, mfojtik, mmccomas, pat.kayongo, sjenning
Target Milestone:	---
Target Release:	3.9.z
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-07-27 10:28:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Patrick Kayongo 2018-07-15 05:12:56 UTC

Description of problem:

I am unable to deploy an application from a private docker hub image. The image stream can correctly read the image (as it gets the image metadata), but the deployment fails.

Version-Release number of selected component (if applicable):

v3.9.31 

How reproducible:



Steps to Reproduce:
oc secrets new my-dockerhub-secret .dockerconfigjson=/root/.docker/config.json
oc secrets add sa/default secrets/my-dockerhub-secret --for=pull
oc new-app --docker-image <registry>/image:tag

Actual results:

I get the following error:

Warning  Failed                 24s (x3 over 1m)  kubelet, node.my.org.co  Failed to pull image "docker.io/myorg/myimage@sha256:5d7....f4": rpc error: code = Unknown desc = repository docker.io/myorg/myimage not found: does not exist or no pull access

Expected results:

A successful deployment.


Additional info:

Comment 1 Michal Fojtik 2018-07-20 12:27:19 UTC

If you have an image stream, why don't you use a image stream change trigger for the deployment config? (Or alternatively you can oc set image).

Comment 2 Xingxing Xia 2018-07-23 06:16:22 UTC

Were reported:
Bug 1561989 (3.10)
Bug 1600539 (3.9)

Comment 3 Patrick Kayongo 2018-07-23 06:36:14 UTC

If a bug has been reported, does this mean a fix can be expected?

Comment 4 Xingxing Xia 2018-07-24 06:23:26 UTC

Looks like the Dev for the Bug 1600539 could give the info.

Comment 5 Maciej Szulik 2018-07-27 10:28:26 UTC

I'm closing this as a duplicate of Bug 1600539.

*** This bug has been marked as a duplicate of bug 1600539 ***