-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test capi-e2e-main-1-28-latest is failing #9633
Comments
Note: This failing test shouldn't necessarily be release blocking as the release v1.6.0 probably won't support Kubernetes v1.29. /triage accepted |
@killianmuldoon what are the kubeadm failure logs exactly? EDIT:
here is the issue that tracks the mentioned job failures:
is it the same problem? |
The kubeadm failure logs are unfortunately buried in CAPD. This is the actual output of a kubeadm join failure:
I was mainly looking at the upstream issue because of the coincidence in time - the 1.28 -> main confromance job has not been flaky or failing recently. It's definitely possible that there's a different cause for this failure. |
The most recent test ran on v1.29.0-alpha.2.787+f5a5d83d7c027a which includes the fix for the Kubeadm issue I linked above. The test failed so it looks like there may be a different underlying issue, possibly in Cluster API itself. Will need to take a closer look into this. |
this definitely seems related to the change in kubernetes/kubernetes#121305 indirectly, this CAPI test job log says that the ClusterRoleBinding called "kubeadm:cluster-admins" was not created during
EDIT: the kubeadm e2e test for this new feature is WIP, but note that we don't have tests that join kubeadm X to kubeadm Y, where X != Y, because that is not a supported skew: |
yep, looks like CAPI has the missing upgrade step. |
Which jobs are failing?
capi-e2e-main-1-28-latest: FAILING
Which tests are failing?
capi-e2e-main-1-28-latest: FAILING
Since when has it been failing?
Since October 27th
Testgrid link
https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api#capi-e2e-main-1-28-latest
Reason for failure (if possible)
No response
Anything else we need to know?
Upstream tests are also failing so this seems directly related to those failures.
Ref: https://testgrid.k8s.io/sig-release-master-informing#periodic-conformance-main-k8s-main
This is the issue tracking this test failure upstream: kubernetes/kubernetes#121617
Label(s) to be applied
/kind failing-test
The text was updated successfully, but these errors were encountered: