Description of problem:
Proxy CI jobs are currently failing like :
Sep 24 03:16:53.079: INFO: 2020-09-24T03:13:20.835804050Z Cloning "git://github.com/openshift/ruby-hello-world.git" ...
2020-09-24T03:13:36.841370114Z WARNING: timed out waiting for git server, will wait 1m4s
2020-09-24T03:14:40.928268255Z WARNING: timed out waiting for git server, will wait 4m16s
2020-09-24T03:16:50.848349366Z error: fatal: unable to connect to github.com:
2020-09-24T03:16:50.848349366Z github.com[0: 18.104.22.168]: errno=Connection timed out
Because our Proxy configuration allows for HTTP and HTTPS requests to be pointed at the egress proxy, but does not allow for Git's native protocol on port 9418 to be proxied out.
Oops, I forgot to link  to https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ocp-4.6-e2e-aws-proxy/1308949438701506560
As part of fixing this bug, we should drop at least this skip .
Verified it using cluster-bot,will check in nightly build again when pr is merged.
(In reply to W. Trevor King from comment #2)
> As part of fixing this bug, we should drop at least this skip .
> : https://github.com/openshift/release/blob/4c9dd40104656afb73e609e3c3d39c0c86bc57b4/ci-operator/step-registry/openshift/e2e/aws/proxy/openshift-e2e-aws-proxy-workflow.yaml#L22
I've filed  to drop the skip.
Hmm, although since we've dropped the skip (for all versions), 4.6 is back to failing on this , e.g. :
$ curl -s https://storage.googleapis.com/origin-ci-test/logs/periodic-ci-openshift-release-master-ocp-4.6-e2e-aws-proxy/1333561788121223168/build-log.txt | grep -A5 'Failing tests:' | head -n6
[sig-api-machinery][Feature:APIServer][Late] kube-apiserver terminates within graceful termination period [Suite:openshift/conformance/parallel]
[sig-arch] Managed cluster should have no crashlooping pods in core namespaces over four minutes [Suite:openshift/conformance/parallel]
[sig-builds][Feature:Builds] build have source revision metadata started build should contain source revision information [Suite:openshift/conformance/parallel]
Not clear to me if we want to backport the fix to 4.6, fork the skips to restore the skip only for 4.6, or just live with 4.6 always failing this step in CI...
*** Bug 1927341 has been marked as a duplicate of this bug. ***
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.
Increasing severity to "medium" as this is impacting proxy tests in CI (and we are adding more of these tests).
*** Bug 1936860 has been marked as a duplicate of this bug. ***