-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
CI: K8sFQDNTest Validate that multiple specs are working correctly #17071
Comments
@nbusseneau it looks like kube-apiserver was crashloopbackoff which caused the test to fail. This was the first test executed after provisioning, the following tests worked / passed successfully [1] . Can we have some sort of sanity check before starting the tests? I thought we did already 🤔 [1] https://jenkins.cilium.io/job/Cilium-PR-K8s-1.21-kernel-4.9/1172/execution/node/168/log/?consoleFull |
Well, we do in the Line 65 in f77996c
Which runs preflight checks: cilium/test/k8sT/assertionHelpers.go Lines 198 to 200 in f77996c
And it seems these were OK here:
So I'm not sure what's going on either 🤔 |
After digging a bit, it seems the various |
This issue has been automatically marked as stale because it has not |
This issue has been automatically marked as stale because it has not |
This issue has not seen any activity since it was marked stale. |
Test Name
Failure Output
Stacktrace
Click to show.
Standard Output
Click to show.
Standard Error
Click to show.
ZIP Links:
Click to show.
https://jenkins.cilium.io/job/Cilium-PR-K8s-1.21-kernel-4.9/1172/artifact/8ca96124_K8sFQDNTest_Validate_that_multiple_specs_are_working_correctly.zip/8ca96124_K8sFQDNTest_Validate_that_multiple_specs_are_working_correctly.zip
https://jenkins.cilium.io/job/Cilium-PR-K8s-1.21-kernel-4.9/1172/artifact/test_results_Cilium-PR-K8s-1.21-kernel-4.9_1172_BDD-Test-PR.zip/test_results_Cilium-PR-K8s-1.21-kernel-4.9_1172_BDD-Test-PR.zip
Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.21-kernel-4.9/1172/
If this is a duplicate of an existing flake, comment 'Duplicate of #<issue-number>' and close this issue.
The text was updated successfully, but these errors were encountered: