Closed maintainer-s-little-helper[bot] closed 1 year ago
PR #22965 hit this flake with 98.61% similarity:
PR #18414 hit this flake with 98.61% similarity:
PR #23276 hit this flake with 96.78% similarity:
PR #23329 hit this flake with 98.61% similarity:
PR #23467 hit this flake with 97.53% similarity:
PR #23612 hit this flake with 94.79% similarity:
PR #23636 hit this flake with 97.53% similarity:
PR #23576 hit this flake with 95.32% similarity:
PR #23956 hit this flake with 95.32% similarity:
PR #24086 hit this flake with 95.32% similarity:
PR #24105 hit this flake with 95.32% similarity:
PR #24105 hit this flake with 95.87% similarity:
PR #24104 hit this flake with 95.87% similarity:
PR #24331 hit this flake with 95.87% similarity:
PR #24331 hit this flake with 95.87% similarity:
PR #24331 hit this flake with 95.87% similarity:
PR #24311 hit this flake with 95.87% similarity:
PR #24387 hit this flake with 97.53% similarity:
PR #24445 hit this flake with 96.99% similarity:
PR #24547 hit this flake with 97.53% similarity:
PR #24550 hit this flake with 94.78% similarity:
PR #24607 hit this flake with 95.32% similarity:
PR #24607 hit this flake with 95.87% similarity:
PR #24547 hit this flake with 97.84% similarity:
PR #24547 hit this flake with 95.87% similarity:
PR #24547 hit this flake with 97.53% similarity:
PR #24789 hit this flake with 95.87% similarity:
PR #24789 hit this flake with 95.87% similarity:
@gandro suggested on Slack that this might be another case similar to https://github.com/cilium/cilium/pull/23334 . If that's the case, we may consider ignoring the error in CI.
PR #24821 hit this flake with 95.87% similarity:
PR #24821 hit this flake with 95.87% similarity:
PR #24831 hit this flake with 95.87% similarity:
PR #24849 hit this flake with 97.53% similarity:
Hit very similar errors in a different test (K8sPolicyTestExtended Validate toEntities KubeAPIServer Allows connection to KubeAPIServer) in https://github.com/cilium/cilium/pull/24785:
2023-04-19T10:30:55.913277228Z level=error msg="Unexpected error when reading response body: net/http: request canceled (Client.Timeout or context cancellation while reading body)" subsys=klog
2023-04-19T10:30:55.913395395Z error retrieving resource lock kube-system/cilium-operator-resource-lock: unexpected error when reading response body. Please retry. Original error: net/http: request canceled (Client.Timeout or context cancellation while reading body)
2023-04-19T10:30:55.913454734Z level=error msg="error retrieving resource lock kube-system/cilium-operator-resource-lock: unexpected error when reading response body. Please retry. Original error: net/http: request canceled (Client.Timeout or context cancellation while reading body)" subsys=klog
Link: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.26-kernel-net-next/1895/testReport/junit/Suite-k8s-1/26/K8sPolicyTestExtended_Validate_toEntities_KubeAPIServer_Allows_connection_to_KubeAPIServer/ Sysdump: e4434197_K8sPolicyTestExtended_Validate_toEntities_KubeAPIServer_Allows_connection_to_KubeAPIServer.zip
Closing this as it's becoming a mix of several very different flakes. We'll reopen with proper issues. Please point to the actual log message failing the test if you hit this again.
Test Name
Failure Output
Stacktrace
Click to show.
```stack-trace /home/jenkins/workspace/Cilium-PR-K8s-1.16-kernel-4.9/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:415 Found 1 io.cilium/app=operator logs matching list of errors that must be investigated: level=error /home/jenkins/workspace/Cilium-PR-K8s-1.16-kernel-4.9/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:413 ```Standard Output
Click to show.
```stack-output Number of "context deadline exceeded" in logs: 0 Number of "level=error" in logs: 0 Number of "level=warning" in logs: 0 Number of "Cilium API handler panicked" in logs: 0 Number of "Goroutine took lock for more than" in logs: 0 No errors/warnings found in logs ⚠️ Found "level=error" in logs 1 times Number of "context deadline exceeded" in logs: 2 Number of "level=error" in logs: 2 Number of "level=warning" in logs: 0 Number of "Cilium API handler panicked" in logs: 0 Number of "Goroutine took lock for more than" in logs: 0 Top 2 errors/warnings: error retrieving resource lock kube-system/cilium-operator-resource-lock: Get \ Interrupt received Number of "context deadline exceeded" in logs: 4 Number of "level=error" in logs: 0 Number of "level=warning" in logs: 5 Number of "Cilium API handler panicked" in logs: 0 Number of "Goroutine took lock for more than" in logs: 0 Top 1 errors/warnings: Unable to restore endpoint, ignoring Cilium pods: [cilium-f9xfj cilium-vt8gd] Netpols loaded: CiliumNetworkPolicies loaded: Endpoint Policy Enforcement: Pod Ingress Egress coredns-8cfc78c54-8l672 false false testclient-75wgd false false testclient-jb9w8 false false testserver-4km8w false false testserver-c7lwn false false grafana-7fd557d749-pgrhf false false prometheus-d87f8f984-k9hz4 false false Cilium agent 'cilium-f9xfj': Status: Ok Health: Ok Nodes "" ContainerRuntime: Kubernetes: Ok KVstore: Ok Controllers: Total 28 Failed 0 Cilium agent 'cilium-vt8gd': Status: Ok Health: Ok Nodes "" ContainerRuntime: Kubernetes: Ok KVstore: Ok Controllers: Total 43 Failed 0 ```Standard Error
Click to show.
```stack-error 12:07:26 STEP: Installing Cilium 12:07:28 STEP: Waiting for Cilium to become ready 12:08:32 STEP: Validating if Kubernetes DNS is deployed 12:08:32 STEP: Checking if deployment is ready 12:08:32 STEP: Checking if kube-dns service is plumbed correctly 12:08:32 STEP: Checking if pods have identity 12:08:32 STEP: Checking if DNS can resolve 12:08:32 STEP: Kubernetes DNS is up and operational 12:08:32 STEP: Validating Cilium Installation 12:08:32 STEP: Performing Cilium controllers preflight check 12:08:32 STEP: Performing Cilium health check 12:08:32 STEP: Performing Cilium status preflight check 12:08:32 STEP: Checking whether host EP regenerated 12:08:33 STEP: Performing Cilium service preflight check 12:08:33 STEP: Performing K8s service preflight check 12:08:34 STEP: Cilium is not ready yet: connectivity health is failing: Cluster connectivity is unhealthy on 'cilium-vt8gd': Exitcode: 1 Err: exit status 1 Stdout: Stderr: Error: Cannot get status/probe: Put "http://%2Fvar%2Frun%2Fcilium%2Fhealth.sock/v1beta/status/probe": dial unix /var/run/cilium/health.sock: connect: no such file or directory command terminated with exit code 1 12:08:34 STEP: Performing Cilium controllers preflight check 12:08:34 STEP: Performing Cilium status preflight check 12:08:34 STEP: Checking whether host EP regenerated 12:08:34 STEP: Performing Cilium health check 12:08:34 STEP: Performing Cilium service preflight check 12:08:34 STEP: Performing K8s service preflight check 12:08:35 STEP: Performing Cilium status preflight check 12:08:35 STEP: Performing Cilium health check 12:08:35 STEP: Performing Cilium controllers preflight check 12:08:35 STEP: Checking whether host EP regenerated 12:08:36 STEP: Performing Cilium service preflight check 12:08:36 STEP: Performing K8s service preflight check 12:08:36 STEP: Performing Cilium status preflight check 12:08:36 STEP: Performing Cilium controllers preflight check 12:08:36 STEP: Checking whether host EP regenerated 12:08:36 STEP: Performing Cilium health check 12:08:37 STEP: Performing Cilium service preflight check 12:08:37 STEP: Performing K8s service preflight check 12:08:38 STEP: Performing Cilium status preflight check 12:08:38 STEP: Performing Cilium controllers preflight check 12:08:38 STEP: Performing Cilium health check 12:08:38 STEP: Checking whether host EP regenerated 12:08:39 STEP: Performing Cilium service preflight check 12:08:39 STEP: Performing K8s service preflight check 12:08:39 STEP: Performing Cilium controllers preflight check 12:08:39 STEP: Performing Cilium status preflight check 12:08:39 STEP: Performing Cilium health check 12:08:39 STEP: Checking whether host EP regenerated 12:08:40 STEP: Performing Cilium service preflight check 12:08:40 STEP: Performing K8s service preflight check 12:08:40 STEP: Performing Cilium controllers preflight check 12:08:40 STEP: Performing Cilium status preflight check 12:08:40 STEP: Performing Cilium health check 12:08:40 STEP: Checking whether host EP regenerated 12:08:41 STEP: Performing Cilium service preflight check 12:08:41 STEP: Performing K8s service preflight check 12:08:42 STEP: Cilium is not ready yet: connectivity health is failing: Cluster connectivity is unhealthy on 'cilium-vt8gd': Exitcode: 1 Err: exit status 1 Stdout: Stderr: Error: Cannot get status/probe: Put "http://%2Fvar%2Frun%2Fcilium%2Fhealth.sock/v1beta/status/probe": dial unix /var/run/cilium/health.sock: connect: no such file or directory command terminated with exit code 1 12:08:42 STEP: Performing Cilium health check 12:08:42 STEP: Performing Cilium controllers preflight check 12:08:42 STEP: Checking whether host EP regenerated 12:08:42 STEP: Performing Cilium status preflight check 12:08:43 STEP: Performing Cilium service preflight check 12:08:43 STEP: Performing K8s service preflight check 12:08:43 STEP: Performing Cilium controllers preflight check 12:08:43 STEP: Performing Cilium status preflight check 12:08:43 STEP: Performing Cilium health check 12:08:43 STEP: Checking whether host EP regenerated 12:08:44 STEP: Performing Cilium service preflight check 12:08:44 STEP: Performing K8s service preflight check 12:08:45 STEP: Performing Cilium status preflight check 12:08:45 STEP: Checking whether host EP regenerated 12:08:45 STEP: Performing Cilium health check 12:08:45 STEP: Performing Cilium controllers preflight check 12:08:45 STEP: Performing Cilium service preflight check 12:08:45 STEP: Performing K8s service preflight check 12:08:47 STEP: Waiting for cilium-operator to be ready 12:08:47 STEP: WaitforPods(namespace="kube-system", filter="-l name=cilium-operator") 12:08:47 STEP: WaitforPods(namespace="kube-system", filter="-l name=cilium-operator") =>ZIP Links:
Click to show.
https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-kernel-4.9//3343/artifact/be2761d8_K8sDatapathConfig_Host_firewall_With_VXLAN.zip https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-kernel-4.9//3343/artifact/test_results_Cilium-PR-K8s-1.16-kernel-4.9_3343_BDD-Test-PR.zipJenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-kernel-4.9/3343/
If this is a duplicate of an existing flake, comment 'Duplicate of #\' and close this issue.