Description of problem: CI jobs are failing with `The unauthenticated git protocol on port 9418 is no longer supported.` Failing job specific to sig-builds: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_console/10341/pull-ci-openshift-console-master-e2e-gcp/1455327531476455424 Sample of failing jobs: https://search.ci.openshift.org/?search=The+unauthenticated+git+protocol+on+port+9418&maxAge=48h&context=1&type=build-log&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job Version-Release number of selected component (if applicable): Numerous 4.x How reproducible: Consistently Steps to Reproduce: 1. Run openshift-tests 2. 3. Actual results: [sig-builds][Feature:Builds] is failing due to reported unsupported git protocol. Expected results: [sig-builds][Feature:Builds] should use supported mechanism for interacting with git. Additional info:
CI jobs are failing with `The unauthenticated git protocol on port 9418 is no longer supported" for s390x as well. Failing job specific to sig-builds: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-multiarch-master-nightly-4.6-ocp-e2e-remote-libvirt-s390x/1455308719846854656 https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-multiarch-master-nightly-4.9-ocp-e2e-remote-libvirt-s390x/1455505091434909696 Sample of failing jobs: https://search.ci.openshift.org/?search=The+unauthenticated+git+protocol+on+port+9418+is+no+longer+supported&maxAge=168h&context=1&type=build-log&name=s390x&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job Version-Release number of selected component (if applicable): Numerous 4.9 & 4.6
I am working on a PR to disable this in 4.10 and backport throughout, but will leave this bugzilla open for a proper fix.
Marking this as a release blocker - given the ubiquity of GitHub we should consider drafting a KCS article to help customers adapt to GitHub's new requirements.
GitHub's announcement they are disabling the `git://` protocol [1]. They are doing this in phases: 1. An initial "brownout", which we hit today (November 2, 2021). 2. A second, longer "brownout" on January 11, 2022. 3. Final shutdown on March 15, 2022. https://github.blog/2021-09-01-improving-git-protocol-security-github
Draft KCS article: https://access.redhat.com/solutions/6628771
KCS approved ... moving to closed/currentrelease