-
Notifications
You must be signed in to change notification settings - Fork 3.8k
CI: K8sFQDNTest BeforeAll fail: Error getting IPs for test #10538
Copy link
Copy link
Closed
Labels
area/CIContinuous Integration testing issue or flakeContinuous Integration testing issue or flakeci/flakeThis is a known failure that occurs in the tree. Please investigate me!This is a known failure that occurs in the tree. Please investigate me!kind/bug/CIThis is a bug in the testing code.This is a bug in the testing code.sig/policyImpacts whether traffic is allowed or denied based on user-defined policies.Impacts whether traffic is allowed or denied based on user-defined policies.
Metadata
Metadata
Labels
area/CIContinuous Integration testing issue or flakeContinuous Integration testing issue or flakeci/flakeThis is a known failure that occurs in the tree. Please investigate me!This is a known failure that occurs in the tree. Please investigate me!kind/bug/CIThis is a bug in the testing code.This is a bug in the testing code.sig/policyImpacts whether traffic is allowed or denied based on user-defined policies.Impacts whether traffic is allowed or denied based on user-defined policies.
CI failure
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/17833/testReport/junit/Suite-k8s-1/11/K8sFQDNTest_Restart_Cilium_validate_that_FQDN_is_still_working/
6b438aba_K8sFQDNTest_Restart_Cilium_validate_that_FQDN_is_still_working.zip
Stacktrace
@jrajahalme @raybejjani I find it interesting that this shows up in PRs shortly after the recent FQDN changes, does this look familiar at all?Initial triage suggests this is unrelated to cilium runtime.