-
Bug
-
Resolution: Done-Errata
-
Minor
-
4.16.0
-
None
-
None
-
No
-
False
-
This is a clone of issue OCPBUGS-30586. The following is the description of the original issue:
—
Description of problem:
CAPI E2Es failing to start in some CAPI provider's release branches.
Failing with the following error: `go: errors parsing go.mod:94/tmp/tmp.ssf1LXKrim/go.mod:5: unknown directive: toolchain` https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_cluster-api/199/pull-ci-openshift-cluster-api-master-e2e-aws-capi-techpreview/1765512397532958720#1:build-log.txt%3A91-95
Version-Release number of selected component (if applicable):
4.15
How reproducible:
Always
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
This is because the script launching the e2e is launching it from the `main` branch of the cluster-capi-operator (which has some backward incompabible go toolchain changes), rather than the correctly matching release branch.
- depends on
-
OCPBUGS-30595 [release-4.15] CAPI E2Es failing to start in some CAPI provider's release branches
- Closed
- is cloned by
-
OCPBUGS-32474 [release-4.13] CAPI E2Es failing to start in some CAPI provider's release branches
- Closed
- links to
-
RHBA-2024:1564 OpenShift Container Platform 4.14.z bug fix update