-
Notifications
You must be signed in to change notification settings - Fork 159
All Windows e2e periodic tests are failing #880
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
Comments
Kept on digging and found out that the
The good logs show that after 10s the kubelet is running however in the logs above it's stopped. |
Looking at the kubelet logs I saw:
For For |
Found out that we have to migrate to containerd in our prow jobs too kubernetes/test-infra#24602 |
the containerd issue was fixed in kubernetes/kubernetes#107189, there's a new issue when the images are built addressed in #884 |
the windows tests are now running https://testgrid.k8s.io/provider-gcp-compute-persistent-disk-csi-driver#ci-win20h2-provider-gcp-compute-persistent-disk-csi-driver, thanks @amacaskill! /close |
@mauriciopoppe: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/reopen I saw that recent runs are failing again https://testgrid.k8s.io/provider-gcp-compute-persistent-disk-csi-driver#ci-windows-2019-provider-gcp-compute-persistent-disk-csi-driver, the logs say:
Comparing with a successful run of Linux (pick a run in https://testgrid.k8s.io/provider-gcp-compute-persistent-disk-csi-driver#Kubernetes%20Master%20Driver%20Latest):
The tests in Windows aren't finding the /cc @alexander-ding |
@mauriciopoppe: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Reading the logs in detail I saw that a different log message in the same line! Windows:
Linux:
It led me to believe that a different version of kubetest2 is used in Windows/Linux, I checked the top of the logs where the script runs and I see this line set only in Linux:
|
Fixed in #1046 |
All the tests are failing for all the Windows versions in https://testgrid.k8s.io/provider-gcp-compute-persistent-disk-csi-driver#ci-win2019-provider-gcp-compute-persistent-disk-csi-driver
From the logs I see that the Windows nodes couldn't join the Kubernetes cluster.
I've also been trying to set up a k/k cluster with Windows nodes in local volume provisioner in this PR kubernetes-sigs/sig-storage-local-static-provisioner#279 which fails with the same error (e.g. nodes not joining the cluster), I couldn't reproduce this locally so I believe it might be something in the GCP project chosen by boskos where the Windows nodepool is created.
Logs from a successful node join:
Logs from the project chosen for the LVP e2e test:
cc @jingxu97
The text was updated successfully, but these errors were encountered: