Bug 1300011

Summary:	Unable to use a git repo for a S2I in a split environment
Product:	OpenShift Container Platform	Reporter:	Eric Jones <erjones>
Component:	Networking	Assignee:	Rajat Chopra <rchopra>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Meng Bo <bmeng>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	3.1.0	CC:	aos-bugs, bbennett, eparis, erjones, spurrier
Target Milestone:	---	Keywords:	UpcomingRelease
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	OpenShift Enterprise 3.1
Last Closed:	2016-03-30 18:09:04 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:

Description Eric Jones 2016-01-19 18:21:00 UTC

Description of problem:
Customer has an OpenShift 3.1 cluster installed with multiple nodes. One is in a private data center and the other is in AWS. If customer attempts to specify a private git repo for use with an S2I, after specifying a secret, the pod never deploys, it hangs on pending waiting to talk with the repo. The node in the private data center is able to, using the same secret, specify the same private git repo for use with an S2I and the pod deploys.

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

How reproducible:
100% in their environment

Steps to Reproduce:
1. Create secret that allows for use with the private git repo
2. Start the S2I deployer 

Actual results:
AWS node deploy hangs

Expected results:
Deploy the node

Additional info:
The customer is able to ssh to each node and manually clone from the git repo in both the AWS and private data center nodes.

Comment 4 Rajat Chopra 2016-03-30 18:09:04 UTC

Closed with fixes gone for release 3.2