Skip to content

CI: K8sDatapathConfig Host firewall With VXLAN and endpoint routes #24698

New issue
New issue
Closed as not planned
Closed as not planned
CI: K8sDatapathConfig Host firewall With VXLAN and endpoint routes#24698
Labels
ci/flakeThis is a known failure that occurs in the tree. Please investigate me!staleThe stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.
@maintainer-s-little-helper

Description

@maintainer-s-little-helper
maintainer-s-little-helper
bot
opened on Apr 3, 2023

Test Name

K8sDatapathConfig Host firewall With VXLAN and endpoint routes

Failure Output

FAIL: cilium pre-flight checks failed

Stacktrace

Click to show. 
/home/jenkins/workspace/Cilium-PR-K8s-1.24-kernel-5.4/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:515
cilium pre-flight checks failed
Expected
    <*errors.errorString | 0xc00068ac40>: {
        s: "Cilium validation failed: 4m0s timeout expired: Last polled error: connectivity health is failing: cilium-agent 'cilium-d2bmq': connectivity to path 'k8s1.host.primary-address.icmp.status' is unhealthy: 'Connection timed out'",
    }
to be nil
/home/jenkins/workspace/Cilium-PR-K8s-1.24-kernel-5.4/src/github.com/cilium/cilium/test/helpers/manifest.go:305

Standard Output

Click to show. 
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
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
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
⚠️  Number of "level=warning" in logs: 6
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
Top 3 errors/warnings:
Disabling socket-LB tracing as it requires kernel 5.7 or newer
Session affinity for host reachable services needs kernel 5.7.0 or newer to work properly when accessed from inside cluster: the same service endpoint will be selected from all network namespaces on the host.
UpdateIdentities: Skipping Delete of a non-existing identity
Cilium pods: [cilium-d2bmq cilium-s28pj]
Netpols loaded: 
CiliumNetworkPolicies loaded: 
Endpoint Policy Enforcement:
Pod                        Ingress   Egress
coredns-6b775575b5-s2b6t   false     false
Cilium agent 'cilium-d2bmq': Status: Ok  Health: Ok Nodes "" ContainerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 24 Failed 0
Cilium agent 'cilium-s28pj': Status: Ok  Health: Ok Nodes "" ContainerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 20 Failed 0

Standard Error

Click to show. 
08:49:04 STEP: Installing Cilium
08:49:06 STEP: Waiting for Cilium to become ready
08:49:27 STEP: Validating if Kubernetes DNS is deployed
08:49:27 STEP: Checking if deployment is ready
08:49:27 STEP: Checking if kube-dns service is plumbed correctly
08:49:27 STEP: Checking if DNS can resolve
08:49:27 STEP: Checking if pods have identity
08:49:31 STEP: Kubernetes DNS is not ready: %!s(<nil>)
08:49:31 STEP: Restarting Kubernetes DNS (-l k8s-app=kube-dns)
08:49:32 STEP: Waiting for Kubernetes DNS to become operational
08:49:32 STEP: Checking if deployment is ready
08:49:32 STEP: Kubernetes DNS is not ready yet: only 0 of 1 replicas are available
08:49:33 STEP: Checking if deployment is ready
08:49:33 STEP: Kubernetes DNS is not ready yet: only 0 of 1 replicas are available
08:49:34 STEP: Checking if deployment is ready
08:49:34 STEP: Kubernetes DNS is not ready yet: only 0 of 1 replicas are available
08:49:35 STEP: Checking if deployment is ready
08:49:35 STEP: Kubernetes DNS is not ready yet: only 0 of 1 replicas are available
08:49:36 STEP: Checking if deployment is ready
08:49:36 STEP: Kubernetes DNS is not ready yet: only 0 of 1 replicas are available
08:49:37 STEP: Checking if deployment is ready
08:49:37 STEP: Checking if kube-dns service is plumbed correctly
08:49:37 STEP: Checking if pods have identity
08:49:37 STEP: Checking if DNS can resolve
08:49:40 STEP: Kubernetes DNS is not ready yet: CiliumEndpoint does not exist
08:49:40 STEP: Checking if deployment is ready
08:49:40 STEP: Checking if kube-dns service is plumbed correctly
08:49:40 STEP: Checking if pods have identity
08:49:40 STEP: Checking if DNS can resolve
08:49:44 STEP: Validating Cilium Installation
08:49:44 STEP: Performing Cilium controllers preflight check
08:49:44 STEP: Performing Cilium health check
08:49:44 STEP: Checking whether host EP regenerated
08:49:44 STEP: Performing Cilium status preflight check
08:49:51 STEP: Performing Cilium service preflight check
08:49:51 STEP: Performing K8s service preflight check
08:49:51 STEP: Cilium is not ready yet: connectivity health is failing: cilium-agent 'cilium-d2bmq': connectivity to path 'k8s1.host.primary-address.icmp.status' is unhealthy: 'Connection timed out'
08:49:51 STEP: Performing Cilium controllers preflight check
08:49:51 STEP: Performing Cilium status preflight check
08:49:51 STEP: Performing Cilium health check
08:49:51 STEP: Checking whether host EP regenerated
08:49:58 STEP: Performing Cilium service preflight check
08:49:58 STEP: Performing K8s service preflight check
08:49:58 STEP: Performing Cilium controllers preflight check
08:49:58 STEP: Performing Cilium health check
08:49:58 STEP: Checking whether host EP regenerated
08:49:58 STEP: Performing Cilium status preflight check
08:50:04 STEP: Performing Cilium service preflight check
08:50:04 STEP: Performing K8s service preflight check
08:50:04 STEP: Performing Cilium health check
08:50:04 STEP: Performing Cilium controllers preflight check
08:50:04 STEP: Performing Cilium status preflight check
08:50:04 STEP: Checking whether host EP regenerated
08:50:11 STEP: Performing Cilium service preflight check
08:50:11 STEP: Performing K8s service preflight check
08:50:11 STEP: Performing Cilium controllers preflight check
08:50:11 STEP: Performing Cilium health check
08:50:11 STEP: Performing Cilium status preflight check
08:50:11 STEP: Checking whether host EP regenerated
08:50:18 STEP: Performing Cilium service preflight check
08:50:18 STEP: Performing K8s service preflight check
08:50:18 STEP: Performing Cilium controllers preflight check
08:50:18 STEP: Performing Cilium health check
08:50:18 STEP: Checking whether host EP regenerated
08:50:18 STEP: Performing Cilium status preflight check
08:50:25 STEP: Performing Cilium service preflight check
08:50:25 STEP: Performing K8s service preflight check
08:50:25 STEP: Performing Cilium controllers preflight check
08:50:25 STEP: Performing Cilium status preflight check
08:50:25 STEP: Performing Cilium health check
08:50:25 STEP: Checking whether host EP regenerated
08:50:32 STEP: Performing Cilium service preflight check
08:50:32 STEP: Performing K8s service preflight check
08:50:32 STEP: Cilium is not ready yet: connectivity health is failing: cilium-agent 'cilium-d2bmq': connectivity to path 'k8s1.host.primary-address.icmp.status' is unhealthy: 'Connection timed out'
08:50:32 STEP: Performing Cilium status preflight check
08:50:32 STEP: Checking whether host EP regenerated
08:50:32 STEP: Performing Cilium health check
08:50:32 STEP: Performing Cilium controllers preflight check
08:50:39 STEP: Performing Cilium service preflight check
08:50:39 STEP: Performing K8s service preflight check
08:50:39 STEP: Performing Cilium controllers preflight check
08:50:39 STEP: Performing Cilium status preflight check
08:50:39 STEP: Performing Cilium health check
08:50:39 STEP: Checking whether host EP regenerated
08:50:46 STEP: Performing Cilium service preflight check
08:50:46 STEP: Performing K8s service preflight check
08:50:46 STEP: Performing Cilium controllers preflight check
08:50:46 STEP: Performing Cilium status preflight check
08:50:46 STEP: Performing Cilium health check
08:50:46 STEP: Checking whether host EP regenerated
08:50:53 STEP: Performing Cilium service preflight check
08:50:53 STEP: Performing K8s service preflight check
08:50:53 STEP: Performing Cilium status preflight check
08:50:53 STEP: Performing Cilium health check
08:50:53 STEP: Checking whether host EP regenerated
08:50:53 STEP: Performing Cilium controllers preflight check
08:51:00 STEP: Performing Cilium service preflight check
08:51:00 STEP: Performing K8s service preflight check
08:51:00 STEP: Performing Cilium controllers preflight check
08:51:00 STEP: Performing Cilium health check
08:51:00 STEP: Performing Cilium status preflight check
08:51:00 STEP: Checking whether host EP regenerated
08:51:06 STEP: Performing Cilium service preflight check
08:51:06 STEP: Performing K8s service preflight check
08:51:06 STEP: Performing Cilium controllers preflight check
08:51:06 STEP: Performing Cilium status preflight check
08:51:06 STEP: Performing Cilium health check
08:51:06 STEP: Checking whether host EP regenerated
08:51:13 STEP: Performing Cilium service preflight check
08:51:13 STEP: Performing K8s service preflight check
08:51:13 STEP: Cilium is not ready yet: connectivity health is failing: cilium-agent 'cilium-d2bmq': connectivity to path 'k8s1.host.primary-address.icmp.status' is unhealthy: 'Connection timed out'
08:51:13 STEP: Performing Cilium controllers preflight check
08:51:13 STEP: Performing Cilium health check
08:51:13 STEP: Performing Cilium status preflight check
08:51:13 STEP: Checking whether host EP regenerated
08:51:20 STEP: Performing Cilium service preflight check
08:51:20 STEP: Performing K8s service preflight check
08:51:20 STEP: Performing Cilium controllers preflight check
08:51:20 STEP: Performing Cilium status preflight check
08:51:20 STEP: Performing Cilium health check
08:51:20 STEP: Checking whether host EP regenerated
08:51:27 STEP: Performing Cilium service preflight check
08:51:27 STEP: Performing K8s service preflight check
08:51:27 STEP: Performing Cilium controllers preflight check
08:51:27 STEP: Performing Cilium health check
08:51:27 STEP: Checking whether host EP regenerated
08:51:27 STEP: Performing Cilium status preflight check
08:51:34 STEP: Performing Cilium service preflight check
08:51:34 STEP: Performing K8s service preflight check
08:51:34 STEP: Performing Cilium controllers preflight check
08:51:34 STEP: Performing Cilium status preflight check
08:51:34 STEP: Performing Cilium health check
08:51:34 STEP: Checking whether host EP regenerated
08:51:41 STEP: Performing Cilium service preflight check
08:51:41 STEP: Performing K8s service preflight check
08:51:41 STEP: Performing Cilium controllers preflight check
08:51:41 STEP: Performing Cilium health check
08:51:41 STEP: Checking whether host EP regenerated
08:51:41 STEP: Performing Cilium status preflight check
08:51:47 STEP: Performing Cilium service preflight check
08:51:47 STEP: Performing K8s service preflight check
08:51:47 STEP: Performing Cilium controllers preflight check
08:51:47 STEP: Performing Cilium status preflight check
08:51:47 STEP: Performing Cilium health check
08:51:47 STEP: Checking whether host EP regenerated
08:51:54 STEP: Performing Cilium service preflight check
08:51:54 STEP: Performing K8s service preflight check
08:51:54 STEP: Cilium is not ready yet: connectivity health is failing: cilium-agent 'cilium-d2bmq': connectivity to path 'k8s1.host.primary-address.icmp.status' is unhealthy: 'Connection timed out'
08:51:54 STEP: Performing Cilium controllers preflight check
08:51:54 STEP: Performing Cilium status preflight check
08:51:54 STEP: Performing Cilium health check
08:51:54 STEP: Checking whether host EP regenerated
08:52:01 STEP: Performing Cilium service preflight check
08:52:01 STEP: Performing K8s service preflight check
08:52:04 STEP: Performing Cilium controllers preflight check
08:52:04 STEP: Performing Cilium health check
08:52:04 STEP: Performing Cilium status preflight check
08:52:04 STEP: Checking whether host EP regenerated
08:52:11 STEP: Performing Cilium service preflight check
08:52:11 STEP: Performing K8s service preflight check
08:52:11 STEP: Performing Cilium controllers preflight check
08:52:11 STEP: Performing Cilium status preflight check
08:52:11 STEP: Performing Cilium health check
08:52:11 STEP: Checking whether host EP regenerated
08:52:18 STEP: Performing Cilium service preflight check
08:52:18 STEP: Performing K8s service preflight check
08:52:18 STEP: Performing Cilium controllers preflight check
08:52:18 STEP: Performing Cilium status preflight check
08:52:18 STEP: Performing Cilium health check
08:52:18 STEP: Checking whether host EP regenerated
08:52:25 STEP: Performing Cilium service preflight check
08:52:25 STEP: Performing K8s service preflight check
08:52:25 STEP: Performing Cilium controllers preflight check
08:52:25 STEP: Performing Cilium health check
08:52:25 STEP: Checking whether host EP regenerated
08:52:25 STEP: Performing Cilium status preflight check
08:52:32 STEP: Performing Cilium service preflight check
08:52:32 STEP: Performing K8s service preflight check
08:52:32 STEP: Performing Cilium controllers preflight check
08:52:32 STEP: Checking whether host EP regenerated
08:52:32 STEP: Performing Cilium status preflight check
08:52:32 STEP: Performing Cilium health check
08:52:39 STEP: Performing Cilium service preflight check
08:52:39 STEP: Performing K8s service preflight check
08:52:39 STEP: Cilium is not ready yet: connectivity health is failing: cilium-agent 'cilium-d2bmq': connectivity to path 'k8s1.host.primary-address.icmp.status' is unhealthy: 'Connection timed out'
08:52:39 STEP: Performing Cilium status preflight check
08:52:39 STEP: Performing Cilium health check
08:52:39 STEP: Performing Cilium controllers preflight check
08:52:39 STEP: Checking whether host EP regenerated
08:52:46 STEP: Performing Cilium service preflight check
08:52:46 STEP: Performing K8s service preflight check
08:52:46 STEP: Performing Cilium status preflight check
08:52:46 STEP: Performing Cilium health check
08:52:46 STEP: Performing Cilium controllers preflight check
08:52:46 STEP: Checking whether host EP regenerated
08:52:52 STEP: Performing Cilium service preflight check
08:52:52 STEP: Performing K8s service preflight check
08:52:52 STEP: Performing Cilium controllers preflight check
08:52:52 STEP: Performing Cilium health check
08:52:52 STEP: Performing Cilium status preflight check
08:52:52 STEP: Checking whether host EP regenerated
08:52:59 STEP: Performing Cilium service preflight check
08:52:59 STEP: Performing K8s service preflight check
08:53:02 STEP: Performing Cilium controllers preflight check
08:53:02 STEP: Performing Cilium health check
08:53:02 STEP: Checking whether host EP regenerated
08:53:02 STEP: Performing Cilium status preflight check
08:53:09 STEP: Performing Cilium service preflight check
08:53:09 STEP: Performing K8s service preflight check
08:53:09 STEP: Performing Cilium controllers preflight check
08:53:09 STEP: Performing Cilium status preflight check
08:53:09 STEP: Performing Cilium health check
08:53:09 STEP: Checking whether host EP regenerated
08:53:15 STEP: Performing Cilium service preflight check
08:53:15 STEP: Performing K8s service preflight check
08:53:15 STEP: Performing Cilium controllers preflight check
08:53:15 STEP: Performing Cilium health check
08:53:15 STEP: Performing Cilium status preflight check
08:53:15 STEP: Checking whether host EP regenerated
08:53:22 STEP: Performing Cilium service preflight check
08:53:22 STEP: Performing K8s service preflight check
08:53:22 STEP: Cilium is not ready yet: connectivity health is failing: cilium-agent 'cilium-d2bmq': connectivity to path 'k8s1.host.primary-address.icmp.status' is unhealthy: 'Connection timed out'
08:53:22 STEP: Performing Cilium status preflight check
08:53:22 STEP: Performing Cilium health check
08:53:22 STEP: Checking whether host EP regenerated
08:53:22 STEP: Performing Cilium controllers preflight check
08:53:29 STEP: Performing Cilium service preflight check
08:53:29 STEP: Performing K8s service preflight check
08:53:29 STEP: Performing Cilium controllers preflight check
08:53:29 STEP: Checking whether host EP regenerated
08:53:29 STEP: Performing Cilium health check
08:53:29 STEP: Performing Cilium status preflight check
08:53:36 STEP: Performing Cilium service preflight check
08:53:36 STEP: Performing K8s service preflight check
08:53:36 STEP: Performing Cilium controllers preflight check
08:53:36 STEP: Performing Cilium health check
08:53:36 STEP: Performing Cilium status preflight check
08:53:36 STEP: Checking whether host EP regenerated
FAIL: cilium pre-flight checks failed
Expected
    <*errors.errorString | 0xc00068ac40>: {
        s: "Cilium validation failed: 4m0s timeout expired: Last polled error: connectivity health is failing: cilium-agent 'cilium-d2bmq': connectivity to path 'k8s1.host.primary-address.icmp.status' is unhealthy: 'Connection timed out'",
    }
to be nil
=== Test Finished at 2023-04-03T08:53:44Z====
08:53:44 STEP: Running JustAfterEach block for EntireTestsuite K8sDatapathConfig
===================== TEST FAILED =====================
08:53:44 STEP: Running AfterFailed block for EntireTestsuite K8sDatapathConfig
cmd: kubectl get pods -o wide --all-namespaces
Exitcode: 0 
Stdout:
 	 NAMESPACE           NAME                               READY   STATUS    RESTARTS   AGE     IP              NODE   NOMINATED NODE   READINESS GATES
	 cilium-monitoring   grafana-84476dcf4b-fz4bg           0/1     Running   0          32m     10.0.0.198      k8s1   <none>           <none>
	 cilium-monitoring   prometheus-7dbb447479-d27j8        1/1     Running   0          32m     10.0.0.184      k8s1   <none>           <none>
	 kube-system         cilium-d2bmq                       1/1     Running   0          4m43s   192.168.56.12   k8s2   <none>           <none>
	 kube-system         cilium-operator-6574d4888c-c5ptj   1/1     Running   0          4m43s   192.168.56.11   k8s1   <none>           <none>
	 kube-system         cilium-operator-6574d4888c-pq7vl   1/1     Running   0          4m43s   192.168.56.12   k8s2   <none>           <none>
	 kube-system         cilium-s28pj                       1/1     Running   0          4m43s   192.168.56.11   k8s1   <none>           <none>
	 kube-system         coredns-6b775575b5-s2b6t           1/1     Running   0          4m17s   10.0.1.242      k8s2   <none>           <none>
	 kube-system         etcd-k8s1                          1/1     Running   0          37m     192.168.56.11   k8s1   <none>           <none>
	 kube-system         kube-apiserver-k8s1                1/1     Running   0          37m     192.168.56.11   k8s1   <none>           <none>
	 kube-system         kube-controller-manager-k8s1       1/1     Running   0          37m     192.168.56.11   k8s1   <none>           <none>
	 kube-system         kube-proxy-vmlzl                   1/1     Running   0          33m     192.168.56.12   k8s2   <none>           <none>
	 kube-system         kube-proxy-xvhrb                   1/1     Running   0          37m     192.168.56.11   k8s1   <none>           <none>
	 kube-system         kube-scheduler-k8s1                1/1     Running   0          37m     192.168.56.11   k8s1   <none>           <none>
	 kube-system         log-gatherer-mdjx9                 1/1     Running   0          32m     192.168.56.11   k8s1   <none>           <none>
	 kube-system         log-gatherer-sztmv                 1/1     Running   0          32m     192.168.56.12   k8s2   <none>           <none>
	 kube-system         registry-adder-njmd9               1/1     Running   0          33m     192.168.56.11   k8s1   <none>           <none>
	 kube-system         registry-adder-t667s               1/1     Running   0          33m     192.168.56.12   k8s2   <none>           <none>
	 
Stderr:
 	 

Fetching command output from pods [cilium-d2bmq cilium-s28pj]
08:53:50 STEP: Performing Cilium service preflight check
08:53:50 STEP: Performing K8s service preflight check
cmd: kubectl exec -n kube-system cilium-d2bmq -c cilium-agent -- cilium status
Exitcode: 0 
Stdout:
 	 KVStore:                 Ok   Disabled
	 Kubernetes:              Ok   1.24 (v1.24.4) [linux/amd64]
	 Kubernetes APIs:         ["cilium/v2::CiliumClusterwideNetworkPolicy", "cilium/v2::CiliumNetworkPolicy", "cilium/v2::CiliumNode", "cilium/v2alpha1::CiliumEndpointSlice", "core/v1::Namespace", "core/v1::Pods", "core/v1::Service", "discovery/v1::EndpointSlice", "networking.k8s.io/v1::NetworkPolicy"]
	 KubeProxyReplacement:    Strict    [enp0s16 192.168.59.15 fd17:625c:f037:2:a00:27ff:fe9b:f1e4, enp0s3 10.0.2.15 fd04::12, enp0s8 192.168.56.12 fd04::12]
	 Host firewall:           Enabled   [enp0s16, enp0s3, enp0s8]
	 CNI Chaining:            none
	 CNI Config file:         CNI configuration file management disabled
	 Cilium:                  Ok   1.13.90 (v1.13.90-4e83f5a8)
	 NodeMonitor:             Listening for events on 3 CPUs with 64x4096 of shared memory
	 Cilium health daemon:    Ok   
	 IPAM:                    IPv4: 3/254 allocated from 10.0.1.0/24, IPv6: 3/254 allocated from fd02::100/120
	 IPv6 BIG TCP:            Disabled
	 BandwidthManager:        Disabled
	 Host Routing:            Legacy
	 Masquerading:            BPF   [enp0s16, enp0s3, enp0s8]   10.0.0.0/8 [IPv4: Enabled, IPv6: Disabled]
	 Controller Status:       24/24 healthy
	 Proxy Status:            OK, ip 10.0.1.187, 0 redirects active on ports 10000-20000
	 Global Identity Range:   min 256, max 65535
	 Hubble:                  Ok   Current/Max Flows: 4284/65535 (6.54%), Flows/s: 16.22   Metrics: Disabled
	 Encryption:              Disabled
	 Cluster health:          1/2 reachable   (2023-04-03T08:53:43Z)
	   Name                   IP              Node          Endpoints
	   k8s1                   192.168.56.11   unreachable   reachable
	 
Stderr:
 	 

cmd: kubectl exec -n kube-system cilium-d2bmq -c cilium-agent -- cilium endpoint list
Exitcode: 0 
Stdout:
 	 ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                                                  IPv6        IPv4         STATUS   
	            ENFORCEMENT        ENFORCEMENT                                                                                                                        
	 367        Disabled           Disabled          18097      k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=kube-system   fd02::175   10.0.1.242   ready   
	                                                            k8s:io.cilium.k8s.policy.cluster=default                                                                      
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=coredns                                                               
	                                                            k8s:io.kubernetes.pod.namespace=kube-system                                                                   
	                                                            k8s:k8s-app=kube-dns                                                                                          
	 1726       Disabled           Disabled          4          reserved:health                                                              fd02::1b8   10.0.1.13    ready   
	 1777       Enabled            Enabled           1          k8s:cilium.io/ci-node=k8s2                                                                            ready   
	                                                            k8s:status=lockdown                                                                                           
	                                                            reserved:host                                                                                                 
	 
Stderr:
 	 

cmd: kubectl exec -n kube-system cilium-s28pj -c cilium-agent -- cilium status
Exitcode: 0 
Stdout:
 	 KVStore:                 Ok   Disabled
	 Kubernetes:              Ok   1.24 (v1.24.4) [linux/amd64]
	 Kubernetes APIs:         ["cilium/v2::CiliumClusterwideNetworkPolicy", "cilium/v2::CiliumNetworkPolicy", "cilium/v2::CiliumNode", "cilium/v2alpha1::CiliumEndpointSlice", "core/v1::Namespace", "core/v1::Pods", "core/v1::Service", "discovery/v1::EndpointSlice", "networking.k8s.io/v1::NetworkPolicy"]
	 KubeProxyReplacement:    Strict    [enp0s16 192.168.59.15 fd17:625c:f037:2:a00:27ff:fed7:e94, enp0s3 10.0.2.15 fd04::11, enp0s8 192.168.56.11 fd04::11]
	 Host firewall:           Enabled   [enp0s16, enp0s3, enp0s8]
	 CNI Chaining:            none
	 CNI Config file:         CNI configuration file management disabled
	 Cilium:                  Ok   1.13.90 (v1.13.90-4e83f5a8)
	 NodeMonitor:             Listening for events on 3 CPUs with 64x4096 of shared memory
	 Cilium health daemon:    Ok   
	 IPAM:                    IPv4: 2/254 allocated from 10.0.0.0/24, IPv6: 2/254 allocated from fd02::/120
	 IPv6 BIG TCP:            Disabled
	 BandwidthManager:        Disabled
	 Host Routing:            Legacy
	 Masquerading:            BPF   [enp0s16, enp0s3, enp0s8]   10.0.0.0/8 [IPv4: Enabled, IPv6: Disabled]
	 Controller Status:       20/20 healthy
	 Proxy Status:            OK, ip 10.0.0.17, 0 redirects active on ports 10000-20000
	 Global Identity Range:   min 256, max 65535
	 Hubble:                  Ok   Current/Max Flows: 6859/65535 (10.47%), Flows/s: 26.11   Metrics: Disabled
	 Encryption:              Disabled
	 Cluster health:          1/2 reachable   (2023-04-03T08:53:42Z)
	   Name                   IP              Node          Endpoints
	   k8s2                   192.168.56.12   unreachable   reachable
	 
Stderr:
 	 

cmd: kubectl exec -n kube-system cilium-s28pj -c cilium-agent -- cilium endpoint list
Exitcode: 0 
Stdout:
 	 ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                                   IPv6       IPv4         STATUS   
	            ENFORCEMENT        ENFORCEMENT                                                                                                        
	 1577       Enabled            Enabled           1          k8s:cilium.io/ci-node=k8s1                                                            ready   
	                                                            k8s:node-role.kubernetes.io/control-plane                                                     
	                                                            k8s:node.kubernetes.io/exclude-from-external-load-balancers                                   
	                                                            k8s:status=lockdown                                                                           
	                                                            reserved:host                                                                                 
	 2814       Disabled           Disabled          4          reserved:health                                               fd02::12   10.0.0.200   ready   
	 
Stderr:
 	 

===================== Exiting AfterFailed =====================
08:53:56 STEP: Running AfterEach for block EntireTestsuite K8sDatapathConfig
08:53:56 STEP: Running AfterEach for block EntireTestsuite

[[ATTACHMENT|aec20a4d_K8sDatapathConfig_Host_firewall_With_VXLAN_and_endpoint_routes.zip]]

ZIP Links:

Click to show.

https://jenkins.cilium.io/job/Cilium-PR-K8s-1.24-kernel-5.4//1553/artifact/0eaf8521_K8sDatapathConfig_Host_firewall_With_native_routing_and_endpoint_routes.zip
https://jenkins.cilium.io/job/Cilium-PR-K8s-1.24-kernel-5.4//1553/artifact/8a16d34d_K8sDatapathConfig_Host_firewall_With_native_routing.zip
https://jenkins.cilium.io/job/Cilium-PR-K8s-1.24-kernel-5.4//1553/artifact/aec20a4d_K8sDatapathConfig_Host_firewall_With_VXLAN_and_endpoint_routes.zip
https://jenkins.cilium.io/job/Cilium-PR-K8s-1.24-kernel-5.4//1553/artifact/d5e33947_K8sDatapathConfig_Host_firewall_With_VXLAN.zip
https://jenkins.cilium.io/job/Cilium-PR-K8s-1.24-kernel-5.4//1553/artifact/test_results_Cilium-PR-K8s-1.24-kernel-5.4_1553_BDD-Test-PR.zip

Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.24-kernel-5.4/1553/

If this is a duplicate of an existing flake, comment 'Duplicate of #<issue-number>' and close this issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    ci/flakeThis is a known failure that occurs in the tree. Please investigate me!staleThe stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions