You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A number of e2e tests - the upgrade test across versions 0.4, 1.0, 1.1 and main - are failing due to the direct download and use of a clusterctl binary that is prone to #6051.
Once we have a release that solves this problem on the older release branches we should update the e2e test configurations in out test definitions in test-infra to use a version of the binary that can complete clusterctl init.
The docker.yaml in the capi repository might also need to be updated (the 0.4 branch appears to use this for the location of the clusterctl binary.
/kind bug
The text was updated successfully, but these errors were encountered:
A number of e2e tests - the upgrade test across versions 0.4, 1.0, 1.1 and main - are failing due to the direct download and use of a clusterctl binary that is prone to #6051.
Once we have a release that solves this problem on the older release branches we should update the e2e test configurations in out test definitions in test-infra to use a version of the binary that can complete
clusterctl init
.The docker.yaml in the capi repository might also need to be updated (the 0.4 branch appears to use this for the location of the clusterctl binary.
/kind bug
The text was updated successfully, but these errors were encountered: