Skip to content

CI: K8sDatapathConfig Host firewall With native routing and endpoint routes #25344

New issue
New issue
Closed
#25374
Closed
CI: K8sDatapathConfig Host firewall With native routing and endpoint routes#25344
#25374
Assignees
tommyp1ckles
Labels
ci/flakeThis is a known failure that occurs in the tree. Please investigate me!
@maintainer-s-little-helper

Description

@maintainer-s-little-helper
maintainer-s-little-helper
bot
opened on May 9, 2023

Test Name

K8sDatapathConfig Host firewall With native routing and endpoint routes

Failure Output

FAIL: cilium pre-flight checks failed

Stacktrace

Click to show. 
/home/jenkins/workspace/Cilium-PR-K8s-1.26-kernel-net-next/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:515
cilium pre-flight checks failed
Expected
    <*errors.errorString | 0xc0037de0d0>: {
        s: "Cilium validation failed: 4m0s timeout expired: Last polled error: connectivity health is failing: cilium-agent 'cilium-gclt9': connectivity to path 'k8s1.host.primary-address.icmp.status' is unhealthy: 'Connection timed out'",
    }
to be nil
/home/jenkins/workspace/Cilium-PR-K8s-1.26-kernel-net-next/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: 2
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
Top 1 errors/warnings:
UpdateIdentities: Skipping Delete of a non-existing identity
Cilium pods: [cilium-gclt9 cilium-qqngb]
Netpols loaded: 
CiliumNetworkPolicies loaded: 
Endpoint Policy Enforcement:
Pod                       Ingress   Egress
coredns-6d97d5ddb-r9hmk   false     false
Cilium agent 'cilium-gclt9': Status: Ok  Health: Ok Nodes "" ContainerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 26 Failed 0
Cilium agent 'cilium-qqngb': Status: Ok  Health: Ok Nodes "" ContainerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 22 Failed 0

Standard Error

Click to show. 
11:50:13 STEP: Installing Cilium
11:50:16 STEP: Waiting for Cilium to become ready
11:50:27 STEP: Validating if Kubernetes DNS is deployed
11:50:27 STEP: Checking if deployment is ready
11:50:28 STEP: Checking if kube-dns service is plumbed correctly
11:50:28 STEP: Checking if DNS can resolve
11:50:28 STEP: Checking if pods have identity
11:50:32 STEP: Kubernetes DNS is not ready: %!s(<nil>)
11:50:32 STEP: Restarting Kubernetes DNS (-l k8s-app=kube-dns)
11:50:33 STEP: Waiting for Kubernetes DNS to become operational
11:50:33 STEP: Checking if deployment is ready
11:50:33 STEP: Kubernetes DNS is not ready yet: only 0 of 1 replicas are available
11:50:34 STEP: Checking if deployment is ready
11:50:34 STEP: Kubernetes DNS is not ready yet: only 0 of 1 replicas are available
11:50:35 STEP: Checking if deployment is ready
11:50:35 STEP: Kubernetes DNS is not ready yet: only 0 of 1 replicas are available
11:50:36 STEP: Checking if deployment is ready
11:50:36 STEP: Kubernetes DNS is not ready yet: only 0 of 1 replicas are available
11:50:37 STEP: Checking if deployment is ready
11:50:37 STEP: Kubernetes DNS is not ready yet: only 0 of 1 replicas are available
11:50:38 STEP: Checking if deployment is ready
11:50:38 STEP: Checking if kube-dns service is plumbed correctly
11:50:38 STEP: Checking if DNS can resolve
11:50:38 STEP: Checking if pods have identity
11:50:42 STEP: Kubernetes DNS is not ready yet: CiliumEndpoint does not exist
11:50:42 STEP: Checking if deployment is ready
11:50:42 STEP: Checking if kube-dns service is plumbed correctly
11:50:42 STEP: Checking if DNS can resolve
11:50:42 STEP: Checking if pods have identity
11:50:46 STEP: Validating Cilium Installation
11:50:46 STEP: Performing Cilium controllers preflight check
11:50:46 STEP: Performing Cilium health check
11:50:46 STEP: Checking whether host EP regenerated
11:50:46 STEP: Performing Cilium status preflight check
11:50:53 STEP: Performing Cilium service preflight check
11:50:53 STEP: Performing K8s service preflight check
11:50:53 STEP: Cilium is not ready yet: connectivity health is failing: cilium-agent 'cilium-gclt9': connectivity to path 'k8s1.host.primary-address.icmp.status' is unhealthy: 'Connection timed out'
11:50:53 STEP: Performing Cilium controllers preflight check
11:50:53 STEP: Performing Cilium status preflight check
11:50:53 STEP: Performing Cilium health check
11:50:53 STEP: Checking whether host EP regenerated
11:51:01 STEP: Performing Cilium service preflight check
11:51:01 STEP: Performing K8s service preflight check
11:51:01 STEP: Performing Cilium controllers preflight check
11:51:01 STEP: Performing Cilium health check
11:51:01 STEP: Performing Cilium status preflight check
11:51:01 STEP: Checking whether host EP regenerated
11:51:09 STEP: Performing Cilium service preflight check
11:51:09 STEP: Performing K8s service preflight check
11:51:09 STEP: Performing Cilium controllers preflight check
11:51:09 STEP: Performing Cilium health check
11:51:09 STEP: Checking whether host EP regenerated
11:51:09 STEP: Performing Cilium status preflight check
11:51:16 STEP: Performing Cilium service preflight check
11:51:16 STEP: Performing K8s service preflight check
11:51:16 STEP: Performing Cilium health check
11:51:16 STEP: Performing Cilium controllers preflight check
11:51:16 STEP: Checking whether host EP regenerated
11:51:16 STEP: Performing Cilium status preflight check
11:51:24 STEP: Performing Cilium service preflight check
11:51:24 STEP: Performing K8s service preflight check
11:51:24 STEP: Performing Cilium controllers preflight check
11:51:24 STEP: Performing Cilium status preflight check
11:51:24 STEP: Performing Cilium health check
11:51:24 STEP: Checking whether host EP regenerated
11:51:32 STEP: Performing Cilium service preflight check
11:51:32 STEP: Performing K8s service preflight check
11:51:32 STEP: Performing Cilium controllers preflight check
11:51:32 STEP: Performing Cilium health check
11:51:32 STEP: Checking whether host EP regenerated
11:51:32 STEP: Performing Cilium status preflight check
11:51:39 STEP: Performing Cilium service preflight check
11:51:39 STEP: Performing K8s service preflight check
11:51:39 STEP: Cilium is not ready yet: connectivity health is failing: cilium-agent 'cilium-gclt9': connectivity to path 'k8s1.host.primary-address.icmp.status' is unhealthy: 'Connection timed out'
11:51:39 STEP: Performing Cilium status preflight check
11:51:39 STEP: Performing Cilium health check
11:51:39 STEP: Performing Cilium controllers preflight check
11:51:39 STEP: Checking whether host EP regenerated
11:51:47 STEP: Performing Cilium service preflight check
11:51:47 STEP: Performing K8s service preflight check
11:51:47 STEP: Performing Cilium controllers preflight check
11:51:47 STEP: Performing Cilium status preflight check
11:51:47 STEP: Performing Cilium health check
11:51:47 STEP: Checking whether host EP regenerated
11:51:54 STEP: Performing Cilium service preflight check
11:51:54 STEP: Performing K8s service preflight check
11:51:54 STEP: Performing Cilium controllers preflight check
11:51:54 STEP: Performing Cilium health check
11:51:54 STEP: Checking whether host EP regenerated
11:51:54 STEP: Performing Cilium status preflight check
11:52:02 STEP: Performing Cilium service preflight check
11:52:02 STEP: Performing K8s service preflight check
11:52:02 STEP: Performing Cilium controllers preflight check
11:52:02 STEP: Performing Cilium health check
11:52:02 STEP: Checking whether host EP regenerated
11:52:02 STEP: Performing Cilium status preflight check
11:52:10 STEP: Performing Cilium service preflight check
11:52:10 STEP: Performing K8s service preflight check
11:52:10 STEP: Performing Cilium controllers preflight check
11:52:10 STEP: Performing Cilium status preflight check
11:52:10 STEP: Performing Cilium health check
11:52:10 STEP: Checking whether host EP regenerated
11:52:17 STEP: Performing Cilium service preflight check
11:52:17 STEP: Performing K8s service preflight check
11:52:17 STEP: Performing Cilium controllers preflight check
11:52:17 STEP: Performing Cilium status preflight check
11:52:17 STEP: Performing Cilium health check
11:52:17 STEP: Checking whether host EP regenerated
11:52:25 STEP: Performing Cilium service preflight check
11:52:25 STEP: Performing K8s service preflight check
11:52:25 STEP: Cilium is not ready yet: connectivity health is failing: cilium-agent 'cilium-gclt9': connectivity to path 'k8s1.host.primary-address.icmp.status' is unhealthy: 'Connection timed out'
11:52:25 STEP: Performing Cilium controllers preflight check
11:52:25 STEP: Checking whether host EP regenerated
11:52:25 STEP: Performing Cilium status preflight check
11:52:25 STEP: Performing Cilium health check
11:52:32 STEP: Performing Cilium service preflight check
11:52:32 STEP: Performing K8s service preflight check
11:52:32 STEP: Performing Cilium controllers preflight check
11:52:32 STEP: Performing Cilium status preflight check
11:52:32 STEP: Checking whether host EP regenerated
11:52:32 STEP: Performing Cilium health check
11:52:40 STEP: Performing Cilium service preflight check
11:52:40 STEP: Performing K8s service preflight check
11:52:40 STEP: Performing Cilium controllers preflight check
11:52:40 STEP: Performing Cilium status preflight check
11:52:40 STEP: Performing Cilium health check
11:52:40 STEP: Checking whether host EP regenerated
11:52:47 STEP: Performing Cilium service preflight check
11:52:47 STEP: Performing K8s service preflight check
11:52:47 STEP: Performing Cilium controllers preflight check
11:52:47 STEP: Performing Cilium health check
11:52:47 STEP: Performing Cilium status preflight check
11:52:47 STEP: Checking whether host EP regenerated
11:52:55 STEP: Performing Cilium service preflight check
11:52:55 STEP: Performing K8s service preflight check
11:52:55 STEP: Performing Cilium controllers preflight check
11:52:55 STEP: Performing Cilium status preflight check
11:52:55 STEP: Performing Cilium health check
11:52:55 STEP: Checking whether host EP regenerated
11:53:03 STEP: Performing Cilium service preflight check
11:53:03 STEP: Performing K8s service preflight check
11:53:03 STEP: Performing Cilium status preflight check
11:53:03 STEP: Performing Cilium health check
11:53:03 STEP: Performing Cilium controllers preflight check
11:53:03 STEP: Checking whether host EP regenerated
11:53:10 STEP: Performing Cilium service preflight check
11:53:10 STEP: Performing K8s service preflight check
11:53:10 STEP: Cilium is not ready yet: connectivity health is failing: cilium-agent 'cilium-gclt9': connectivity to path 'k8s1.host.primary-address.icmp.status' is unhealthy: 'Connection timed out'
11:53:10 STEP: Performing Cilium controllers preflight check
11:53:10 STEP: Performing Cilium status preflight check
11:53:10 STEP: Performing Cilium health check
11:53:10 STEP: Checking whether host EP regenerated
11:53:25 STEP: Performing Cilium service preflight check
11:53:25 STEP: Performing K8s service preflight check
11:53:25 STEP: Performing Cilium controllers preflight check
11:53:25 STEP: Performing Cilium status preflight check
11:53:25 STEP: Performing Cilium health check
11:53:25 STEP: Checking whether host EP regenerated
11:53:32 STEP: Performing Cilium service preflight check
11:53:32 STEP: Performing K8s service preflight check
11:53:32 STEP: Performing Cilium controllers preflight check
11:53:32 STEP: Performing Cilium status preflight check
11:53:32 STEP: Performing Cilium health check
11:53:32 STEP: Checking whether host EP regenerated
11:53:40 STEP: Performing Cilium service preflight check
11:53:40 STEP: Performing K8s service preflight check
11:53:40 STEP: Performing Cilium controllers preflight check
11:53:40 STEP: Performing Cilium status preflight check
11:53:40 STEP: Performing Cilium health check
11:53:40 STEP: Checking whether host EP regenerated
11:53:47 STEP: Performing Cilium service preflight check
11:53:47 STEP: Performing K8s service preflight check
11:53:47 STEP: Performing Cilium controllers preflight check
11:53:47 STEP: Performing Cilium health check
11:53:47 STEP: Checking whether host EP regenerated
11:53:47 STEP: Performing Cilium status preflight check
11:53:55 STEP: Performing Cilium service preflight check
11:53:55 STEP: Performing K8s service preflight check
11:53:55 STEP: Performing Cilium controllers preflight check
11:53:55 STEP: Performing Cilium health check
11:53:55 STEP: Checking whether host EP regenerated
11:53:55 STEP: Performing Cilium status preflight check
11:54:09 STEP: Performing Cilium service preflight check
11:54:09 STEP: Performing K8s service preflight check
11:54:09 STEP: Cilium is not ready yet: connectivity health is failing: cilium-agent 'cilium-gclt9': connectivity to path 'k8s1.host.primary-address.icmp.status' is unhealthy: 'Connection timed out'
11:54:09 STEP: Performing Cilium controllers preflight check
11:54:09 STEP: Performing Cilium health check
11:54:09 STEP: Checking whether host EP regenerated
11:54:09 STEP: Performing Cilium status preflight check
11:54:17 STEP: Performing Cilium service preflight check
11:54:17 STEP: Performing K8s service preflight check
11:54:17 STEP: Performing Cilium controllers preflight check
11:54:17 STEP: Performing Cilium health check
11:54:17 STEP: Performing Cilium status preflight check
11:54:17 STEP: Checking whether host EP regenerated
11:54:24 STEP: Performing Cilium service preflight check
11:54:24 STEP: Performing K8s service preflight check
11:54:24 STEP: Performing Cilium controllers preflight check
11:54:24 STEP: Performing Cilium status preflight check
11:54:24 STEP: Performing Cilium health check
11:54:24 STEP: Checking whether host EP regenerated
11:54:32 STEP: Performing Cilium service preflight check
11:54:32 STEP: Performing K8s service preflight check
11:54:32 STEP: Performing Cilium controllers preflight check
11:54:32 STEP: Performing Cilium status preflight check
11:54:32 STEP: Performing Cilium health check
11:54:32 STEP: Checking whether host EP regenerated
11:54:39 STEP: Performing Cilium service preflight check
11:54:39 STEP: Performing K8s service preflight check
11:54:39 STEP: Performing Cilium controllers preflight check
11:54:39 STEP: Performing Cilium status preflight check
11:54:39 STEP: Performing Cilium health check
11:54:39 STEP: Checking whether host EP regenerated
FAIL: cilium pre-flight checks failed
Expected
    <*errors.errorString | 0xc0037de0d0>: {
        s: "Cilium validation failed: 4m0s timeout expired: Last polled error: connectivity health is failing: cilium-agent 'cilium-gclt9': connectivity to path 'k8s1.host.primary-address.icmp.status' is unhealthy: 'Connection timed out'",
    }
to be nil
=== Test Finished at 2023-05-09T11:54:46Z====
11:54:46 STEP: Running JustAfterEach block for EntireTestsuite K8sDatapathConfig
===================== TEST FAILED =====================
11:54:47 STEP: Running AfterFailed block for EntireTestsuite K8sDatapathConfig
11:54:47 STEP: Performing Cilium service preflight check
11:54:47 STEP: Performing K8s service preflight check
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-67ff49cd99-6vjgl           0/1     Running   0          55m     10.0.0.108      k8s1   <none>           <none>
	 cilium-monitoring   prometheus-8c7df94b4-t2df2         1/1     Running   0          55m     10.0.0.113      k8s1   <none>           <none>
	 kube-system         cilium-gclt9                       1/1     Running   0          4m36s   192.168.56.12   k8s2   <none>           <none>
	 kube-system         cilium-operator-7bc6974595-5c9sk   1/1     Running   0          4m36s   192.168.56.13   k8s3   <none>           <none>
	 kube-system         cilium-operator-7bc6974595-nbz62   1/1     Running   0          4m36s   192.168.56.12   k8s2   <none>           <none>
	 kube-system         cilium-qqngb                       1/1     Running   0          4m36s   192.168.56.11   k8s1   <none>           <none>
	 kube-system         coredns-6d97d5ddb-r9hmk            1/1     Running   0          4m19s   10.0.0.39       k8s2   <none>           <none>
	 kube-system         etcd-k8s1                          1/1     Running   0          63m     192.168.56.11   k8s1   <none>           <none>
	 kube-system         kube-apiserver-k8s1                1/1     Running   0          63m     192.168.56.11   k8s1   <none>           <none>
	 kube-system         kube-controller-manager-k8s1       1/1     Running   0          63m     192.168.56.11   k8s1   <none>           <none>
	 kube-system         kube-scheduler-k8s1                1/1     Running   0          63m     192.168.56.11   k8s1   <none>           <none>
	 kube-system         log-gatherer-gxlpz                 1/1     Running   0          56m     192.168.56.12   k8s2   <none>           <none>
	 kube-system         log-gatherer-n2rkv                 1/1     Running   0          56m     192.168.56.13   k8s3   <none>           <none>
	 kube-system         log-gatherer-xxzgr                 1/1     Running   0          56m     192.168.56.11   k8s1   <none>           <none>
	 kube-system         registry-adder-7fgns               1/1     Running   0          56m     192.168.56.13   k8s3   <none>           <none>
	 kube-system         registry-adder-tnnnx               1/1     Running   0          56m     192.168.56.12   k8s2   <none>           <none>
	 kube-system         registry-adder-trlbd               1/1     Running   0          56m     192.168.56.11   k8s1   <none>           <none>
	 
Stderr:
 	 

Fetching command output from pods [cilium-gclt9 cilium-qqngb]
cmd: kubectl exec -n kube-system cilium-gclt9 -c cilium-agent -- cilium status
Exitcode: 0 
Stdout:
 	 KVStore:                 Ok   Disabled
	 Kubernetes:              Ok   1.26 (v1.26.3) [linux/amd64]
	 Kubernetes APIs:         ["cilium/v2::CiliumClusterwideNetworkPolicy", "cilium/v2::CiliumNetworkPolicy", "cilium/v2::CiliumNode", "cilium/v2alpha1::CiliumCIDRGroup", "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:fe8d:46df, enp0s3 10.0.2.15 fd04::12, enp0s8 192.168.56.12 fd04::12 (Direct Routing)]
	 Host firewall:           Enabled   [enp0s16, enp0s3, enp0s8]
	 CNI Chaining:            none
	 Cilium:                  Ok   1.14.0-dev (v1.14.0-dev-361e634c)
	 NodeMonitor:             Listening for events on 3 CPUs with 64x4096 of shared memory
	 Cilium health daemon:    Ok   
	 IPAM:                    IPv4: 3/254 allocated from 10.0.0.0/24, IPv6: 3/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:       26/26 healthy
	 Proxy Status:            OK, ip 10.0.0.124, 0 redirects active on ports 10000-20000
	 Global Identity Range:   min 256, max 65535
	 Hubble:                  Ok              Current/Max Flows: 4145/65535 (6.32%), Flows/s: 15.38   Metrics: Disabled
	 Encryption:              Disabled        
	 Cluster health:          1/2 reachable   (2023-05-09T11:54:46Z)
	   Name                   IP              Node          Endpoints
	   k8s1                   192.168.56.11   unreachable   reachable
	 
Stderr:
 	 

cmd: kubectl exec -n kube-system cilium-gclt9 -c cilium-agent -- cilium endpoint list
Exitcode: 0 
Stdout:
 	 ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                                                  IPv6       IPv4         STATUS   
	            ENFORCEMENT        ENFORCEMENT                                                                                                                       
	 593        Enabled            Enabled           1          k8s:cilium.io/ci-node=k8s2                                                                           ready   
	                                                            k8s:status=lockdown                                                                                          
	                                                            reserved:host                                                                                                
	 955        Disabled           Disabled          4          reserved:health                                                              fd02::da   10.0.0.184   ready   
	 1630       Disabled           Disabled          3831       k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=kube-system   fd02::bf   10.0.0.39    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                                                                                         
	 
Stderr:
 	 

cmd: kubectl exec -n kube-system cilium-qqngb -c cilium-agent -- cilium status
Exitcode: 0 
Stdout:
 	 KVStore:                 Ok   Disabled
	 Kubernetes:              Ok   1.26 (v1.26.3) [linux/amd64]
	 Kubernetes APIs:         ["cilium/v2::CiliumClusterwideNetworkPolicy", "cilium/v2::CiliumNetworkPolicy", "cilium/v2::CiliumNode", "cilium/v2alpha1::CiliumCIDRGroup", "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:fead:5b39, enp0s3 10.0.2.15 fd04::11, enp0s8 192.168.56.11 fd04::11 (Direct Routing)]
	 Host firewall:           Enabled   [enp0s16, enp0s3, enp0s8]
	 CNI Chaining:            none
	 Cilium:                  Ok   1.14.0-dev (v1.14.0-dev-361e634c)
	 NodeMonitor:             Listening for events on 3 CPUs with 64x4096 of shared memory
	 Cilium health daemon:    Ok   
	 IPAM:                    IPv4: 2/254 allocated from 10.0.1.0/24, IPv6: 2/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:       22/22 healthy
	 Proxy Status:            OK, ip 10.0.1.152, 0 redirects active on ports 10000-20000
	 Global Identity Range:   min 256, max 65535
	 Hubble:                  Ok              Current/Max Flows: 6682/65535 (10.20%), Flows/s: 24.93   Metrics: Disabled
	 Encryption:              Disabled        
	 Cluster health:          1/2 reachable   (2023-05-09T11:53:37Z)
	   Name                   IP              Node          Endpoints
	   k8s2                   192.168.56.12   unreachable   reachable
	 
Stderr:
 	 

cmd: kubectl exec -n kube-system cilium-qqngb -c cilium-agent -- cilium endpoint list
Exitcode: 0 
Stdout:
 	 ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                                   IPv6        IPv4        STATUS   
	            ENFORCEMENT        ENFORCEMENT                                                                                                        
	 783        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                                                                                 
	 1447       Disabled           Disabled          4          reserved:health                                               fd02::166   10.0.1.43   ready   
	 
Stderr:
 	 

===================== Exiting AfterFailed =====================
11:55:02 STEP: Running AfterEach for block EntireTestsuite K8sDatapathConfig
11:55:02 STEP: Running AfterEach for block EntireTestsuite

[[ATTACHMENT|bf448f31_K8sDatapathConfig_Host_firewall_With_native_routing_and_endpoint_routes.zip]]
11:55:04 STEP: Running AfterAll block for EntireTestsuite K8sDatapathConfig Host firewall

ZIP Links:

Click to show.

https://jenkins.cilium.io/job/Cilium-PR-K8s-1.26-kernel-net-next//2154/artifact/024b6c05_K8sDatapathConfig_Host_firewall_With_VXLAN_and_endpoint_routes.zip
https://jenkins.cilium.io/job/Cilium-PR-K8s-1.26-kernel-net-next//2154/artifact/913c5175_K8sDatapathServicesTest_Checks_N-S_loadbalancing_With_host_policy_Tests_NodePort.zip
https://jenkins.cilium.io/job/Cilium-PR-K8s-1.26-kernel-net-next//2154/artifact/bf448f31_K8sDatapathConfig_Host_firewall_With_native_routing_and_endpoint_routes.zip
https://jenkins.cilium.io/job/Cilium-PR-K8s-1.26-kernel-net-next//2154/artifact/c1880546_K8sDatapathConfig_Host_firewall_With_native_routing.zip
https://jenkins.cilium.io/job/Cilium-PR-K8s-1.26-kernel-net-next//2154/artifact/test_results_Cilium-PR-K8s-1.26-kernel-net-next_2154_BDD-Test-PR.zip

Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.26-kernel-net-next/2154/

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

Metadata

Metadata

Assignees

Labels

ci/flakeThis is a known failure that occurs in the tree. Please investigate me!

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions