The initial installation of Cilium in the test sometimes times out. We can see that it eventually became ready because the agents are reporting a ready status in the sysdump.
Stacktrace
/home/jenkins/workspace/Cilium-PR-K8s-1.26-kernel-net-next/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:453
cilium pre-flight checks failed
Expected
<*errors.errorString | 0xc002153860>: {
s: "Cilium validation failed: 4m0s timeout expired: Last polled error: connectivity health is failing: cilium-agent 'cilium-rnv46': connectivity to path 'k8s2.health-endpoint.secondary-addresses[*].icmp.status' is unhealthy: 'Connection timed out'",
}
to be nil
Jenkins: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.26-kernel-net-next/519/testReport/junit/Suite-k8s-1/26/K8sDatapathServicesTest_Checks_device_reconfiguration_Detects_newly_added_device_and_reloads_datapath/
Sysdump:
cilium-sysdump.7z.zip
Given the nature of the test (literally Detects newly added device and reloads datapath), the tested feature could explain the additional delay. It would be good to confirm and either fix it or extend the timeout for that specific test.
cc @joamaki
The initial installation of Cilium in the test sometimes times out. We can see that it eventually became ready because the agents are reporting a ready status in the sysdump.
Jenkins: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.26-kernel-net-next/519/testReport/junit/Suite-k8s-1/26/K8sDatapathServicesTest_Checks_device_reconfiguration_Detects_newly_added_device_and_reloads_datapath/
Sysdump:
cilium-sysdump.7z.zip
Given the nature of the test (literally
Detects newly added device and reloads datapath), the tested feature could explain the additional delay. It would be good to confirm and either fix it or extend the timeout for that specific test.cc @joamaki