Description of problem: oc new-app with the different way of parameter passing should have consistent behavior Version-Release number of selected component (if applicable): oc v3.9.0-0.16.0 kubernetes v1.9.0-beta1 features: Basic-Auth GSSAPI Kerberos SPNEGO How reproducible: Always Steps to Reproduce: 1. oc new-app openshift/ruby:latest~https://github.com/openshift/fakerepo.git 2. oc new-app --image-stream=openshift/ruby:latest --code=https://github.com/openshift/fakerepo.git 3. Actual results: 1. Could build up the components of an application successfully without GitHub user/password 2. need GitHub user/password Expected results: These two ways should have consistent behavior. Additional info:
Since it wasn't clear to me.. the issue here is not that the app ultimately doesn't build, it's that in (1) the components of the app are successfully created (even though the repo does not exist) and in (2) the components are not created because we can't clone the repo. MJ, I think this is related to https://bugzilla.redhat.com/show_bug.cgi?id=1470374
It might be solved already. I will check and confirm.
I suspect the problem root cause is similar. Its problem here: https://github.com/openshift/origin/blob/master/pkg/git/repository.go#L228 So its different issue, but same "source code detection flow". We can work it by adding some error checking here: https://github.com/openshift/origin/blob/master/pkg/oc/generate/cmd/resolve.go#L264 Which would "/dev/null" errors, if they come from certain git behavior. In example: 1. No git available. 2. Remote repo is secure. Any other errors would be threaded as normal errors and passed down the stream for proper handling. Overall some of the oc & git interaction should be revisited?
doing a small bugfix, which might solve this too https://bugzilla.redhat.com/show_bug.cgi?id=1470374
*** This bug has been marked as a duplicate of bug 1470374 ***