Bug 1360900

Summary:	OpenShift unable to pull containerized components from secure private registry
Product:	OpenShift Container Platform	Reporter:	broskos
Component:	RFE	Assignee:	Jason DeTiberus <jdetiber>
Status:	CLOSED DUPLICATE	QA Contact:	Johnny Liu <jialiu>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.2.0	CC:	aos-bugs, broskos, jokerman, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-02 06:05:06 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 broskos 2016-07-27 18:43:54 UTC

Description of problem:
OpenShift is unable to use a password secured private registry from containerized components like ose-pod, ose-deployer, etc

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

How reproducible:
Always

Steps to Reproduce:
1. Perform a disconnected installation according to the online docs
2. After installation point docker to your secured private registry
3. create a secret with oc secrets new dockercfg
4. perform container deployment on node without a pre-cached copy of ose-pod

Actual results:
container deployment fails, ose-pod is never pulled from secure private registry

Expected results:
container deployment should succeed, pulling ose-pod and any other needed containerized components from secure private repository.

Additional info:

Comment 1 Johnny Liu 2016-08-02 06:03:16 UTC

Seem like this bug is duplicated with BZ#1316341.

Comment 2 Johnny Liu 2016-08-02 06:05:06 UTC


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