+++ This bug was initially created as a clone of Bug #1894796 +++
Description of problem:
There is another problem they are facing after the upgrade. All the S2I builds from their private source git repositry which we have access from openshift environment are failing with the following git error.
We are only able to see below build failure log (attached full log).
error: only one config file at a time.
usage: git config [<options>]
Build fails to clone source from private git repo.
Builds should clone from private git repo.
*** Bug 1896801 has been marked as a duplicate of this bug. ***
Created article with workaround: https://access.redhat.com/solutions/5571661
Work around is to set a cluster BuildDefault to clear the proxy settings for git cloning:
$ oc edit build.config.openshift.io/cluster
Note that this works if access to the git repository bypasses the proxy via the NO_PROXY environment variable. If the cluster requires the proxy to access all external applications, then this solution would not be applicable.
Launched a 4.7 proxy cluster, using image built from build #189.
With .gitconfig of source secret , build could pull code from private repo. Builds go to completed.
With basic auth of source secret, build could pull code from private repo. Builds go to completed.
Basic HTTP auth with token, github.com added to NO_PROXY. Times out cloning source (cannot access github.com)
Marking Bug 1873327 as a related issue, but not a blocker.
Verified on 4.7.0-0.nightly-2020-11-25-114114 proxy cluster.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
Removing UpgradeBlocker from this older bug, to remove it from the suspect queue described in . If you feel like this bug still needs to be a suspect, please add keyword again.