Bug 1896801 - Can't get code from GIT using a proxy and a secret with credentials
Summary: Can't get code from GIT using a proxy and a secret with credentials
Keywords:
Status: CLOSED DUPLICATE of bug 1896446
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Build
Version: 4.6.z
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.7.0
Assignee: Gabe Montero
QA Contact: XiuJuan Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-11 15:04 UTC by Sergio G.
Modified: 2023-12-15 20:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-11 16:12:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
buildconfig (544 bytes, text/plain)
2020-11-11 15:04 UTC, Sergio G.
no flags Details
full log of the failed build (14.15 KB, text/plain)
2020-11-11 15:04 UTC, Sergio G.
no flags Details

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 ***


Note You need to log in before you can comment on or make changes to this bug.