cluster-api-provider-vsphere
cluster-api-provider-vsphere copied to clipboard
CI: e2e test in node_labeling_test.go is flaky
trafficstars
/kind bug
What steps did you take and what happened: [A clear and concise description of what the bug is.]
The prowjob periodic-e2e-main shows 2/14 failed jobs for the test:
capv-e2e.[It] Label nodes with ESXi host info creates a workload cluster whose nodes have the ESXi host info
Occurencies on the same commit which is still the same as main today:
- https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/periodic-cluster-api-provider-vsphere-e2e-main/1673752791283142656
- https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/periodic-cluster-api-provider-vsphere-e2e-main/1674115183494041600
Also on PR #1970 this test failed with the same results.
Going some more back in history:
- The flaky test seems to already have existed back in April
What did you expect to happen:
The test to succeed / not being flaky.
Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
Environment:
- Cluster-api-provider-vsphere version:
- Kubernetes version: (use
kubectl version): - OS (e.g. from
/etc/os-release):