Bug 1896801

Summary: Can't get code from GIT using a proxy and a secret with credentials
Product: OpenShift Container Platform Reporter: Sergio G. <sgarciam>
Component: BuildAssignee: Gabe Montero <gmontero>
Status: CLOSED DUPLICATE QA Contact: XiuJuan Wang <xiuwang>
Severity: high Docs Contact:
Priority: high    
Version: 4.6.zCC: aos-bugs
Target Milestone: ---   
Target Release: 4.7.0   
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: 2020-11-11 16:12:33 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:
Attachments:
Description Flags
buildconfig
none
full log of the failed build none

Description Sergio G. 2020-11-11 15:04:20 UTC
Created attachment 1728361 [details]
buildconfig

Description of problem:
Builds which require a proxy (from cluster-wide or per build configuration) and a secret with credentials fail.

See attached there's the full trace of such build and the definition.


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


How reproducible:
Always


Steps to reproduce:
1. oc new-project sgarcia-test1
2. oc apply -f buildconfig.yaml
3. oc start-build --build-loglevel 7 -F nodejs-ex


Actual results:
The build is unable to configure the proxy and the credentials from a secret.


Expected results:
The build should succeed.

Notes:
 - FWIW the same steps work without issues in OpenShift 4.5.16.
 - The same buildconfig with a repository which doesn't requires credentials (but a proxy) works.
 - The same buildconfig without the proxy (but with credentials) works.
 - It's the combination of the two configuration sources which causes the fail.

Comment 1 Sergio G. 2020-11-11 15:04:59 UTC
Created attachment 1728362 [details]
full log of the failed build

Comment 2 Adam Kaplan 2020-11-11 15:43:21 UTC
This probably duplicates https://bugzilla.redhat.com/show_bug.cgi?id=1896446. Looks like we have the same scenario - git clone from private repository, cluster is behind a proxy.

Comment 3 Gabe Montero 2020-11-11 16:12:12 UTC
the log with trace here was very helpful though :-) ... we were trying to get it from the other customer

we've started working on a fix

Comment 4 Gabe Montero 2020-11-11 16:12:33 UTC

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