CI: K8sDatapathConfig Host firewall With native routing #24699
Description
Test Name
K8sDatapathConfig Host firewall With native routing
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 | 0xc00242d030>: {
s: "Cilium validation failed: 4m0s timeout expired: Last polled error: connectivity health is failing: cilium-agent 'cilium-5zg7d': 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-5zg7d cilium-7q4z4]
Netpols loaded:
CiliumNetworkPolicies loaded:
Endpoint Policy Enforcement:
Pod Ingress Egress
coredns-6b775575b5-hgkt5 false false
Cilium agent 'cilium-5zg7d': Status: Ok Health: Ok Nodes "" ContainerRuntime: Kubernetes: Ok KVstore: Ok Controllers: Total 21 Failed 0
Cilium agent 'cilium-7q4z4': Status: Ok Health: Ok Nodes "" ContainerRuntime: Kubernetes: Ok KVstore: Ok Controllers: Total 25 Failed 0
Standard Error
Click to show.
08:53:58 STEP: Installing Cilium
08:54:01 STEP: Waiting for Cilium to become ready
08:54:15 STEP: Validating if Kubernetes DNS is deployed
08:54:15 STEP: Checking if deployment is ready
08:54:15 STEP: Checking if kube-dns service is plumbed correctly
08:54:15 STEP: Checking if DNS can resolve
08:54:15 STEP: Checking if pods have identity
08:54:31 STEP: Kubernetes DNS is not ready: unable to resolve service name kubernetes.default.svc.cluster.local with DNS server 10.96.0.10 by running 'dig +short kubernetes.default.svc.cluster.local @10.96.0.10' Cilium pod: Exitcode: 9
Err: exit status 9
Stdout:
;; connection timed out; no servers could be reached
Stderr:
command terminated with exit code 9
08:54:31 STEP: Restarting Kubernetes DNS (-l k8s-app=kube-dns)
08:54:31 STEP: Waiting for Kubernetes DNS to become operational
08:54:31 STEP: Checking if deployment is ready
08:54:31 STEP: Kubernetes DNS is not ready yet: only 0 of 1 replicas are available
08:54:32 STEP: Checking if deployment is ready
08:54:32 STEP: Kubernetes DNS is not ready yet: only 0 of 1 replicas are available
08:54:33 STEP: Checking if deployment is ready
08:54:33 STEP: Checking if kube-dns service is plumbed correctly
08:54:33 STEP: Checking if DNS can resolve
08:54:33 STEP: Checking if pods have identity
08:54:36 STEP: Validating Cilium Installation
08:54:36 STEP: Performing Cilium controllers preflight check
08:54:36 STEP: Performing Cilium health check
08:54:36 STEP: Performing Cilium status preflight check
08:54:36 STEP: Checking whether host EP regenerated
08:54:43 STEP: Performing Cilium service preflight check
08:54:43 STEP: Performing K8s service preflight check
08:54:43 STEP: Cilium is not ready yet: connectivity health is failing: cilium-agent 'cilium-5zg7d': connectivity to path 'k8s1.host.primary-address.icmp.status' is unhealthy: 'Connection timed out'
08:54:43 STEP: Performing Cilium status preflight check
08:54:43 STEP: Performing Cilium health check
08:54:43 STEP: Checking whether host EP regenerated
08:54:43 STEP: Performing Cilium controllers preflight check
08:54:50 STEP: Performing Cilium service preflight check
08:54:50 STEP: Performing K8s service preflight check
08:54:50 STEP: Performing Cilium controllers preflight check
08:54:50 STEP: Performing Cilium status preflight check
08:54:50 STEP: Checking whether host EP regenerated
08:54:50 STEP: Performing Cilium health check
08:54:57 STEP: Performing Cilium service preflight check
08:54:57 STEP: Performing K8s service preflight check
08:54:57 STEP: Performing Cilium controllers preflight check
08:54:57 STEP: Performing Cilium health check
08:54:57 STEP: Performing Cilium status preflight check
08:54:57 STEP: Checking whether host EP regenerated
08:55:04 STEP: Performing Cilium service preflight check
08:55:04 STEP: Performing K8s service preflight check
08:55:04 STEP: Performing Cilium controllers preflight check
08:55:04 STEP: Performing Cilium health check
08:55:04 STEP: Checking whether host EP regenerated
08:55:04 STEP: Performing Cilium status preflight check
08:55:11 STEP: Performing Cilium service preflight check
08:55:11 STEP: Performing K8s service preflight check
08:55:11 STEP: Performing Cilium status preflight check
08:55:11 STEP: Performing Cilium health check
08:55:11 STEP: Checking whether host EP regenerated
08:55:11 STEP: Performing Cilium controllers preflight check
08:55:18 STEP: Performing Cilium service preflight check
08:55:18 STEP: Performing K8s service preflight check
08:55:18 STEP: Performing Cilium controllers preflight check
08:55:18 STEP: Performing Cilium status preflight check
08:55:18 STEP: Checking whether host EP regenerated
08:55:18 STEP: Performing Cilium health check
08:55:25 STEP: Performing Cilium service preflight check
08:55:25 STEP: Performing K8s service preflight check
08:55:25 STEP: Cilium is not ready yet: connectivity health is failing: cilium-agent 'cilium-5zg7d': connectivity to path 'k8s1.host.primary-address.icmp.status' is unhealthy: 'Connection timed out'
08:55:25 STEP: Performing Cilium controllers preflight check
08:55:25 STEP: Performing Cilium health check
08:55:25 STEP: Checking whether host EP regenerated
08:55:25 STEP: Performing Cilium status preflight check
08:55:31 STEP: Performing Cilium service preflight check
08:55:31 STEP: Performing K8s service preflight check
08:55:31 STEP: Performing Cilium controllers preflight check
08:55:31 STEP: Performing Cilium health check
08:55:31 STEP: Checking whether host EP regenerated
08:55:31 STEP: Performing Cilium status preflight check
08:55:38 STEP: Performing Cilium service preflight check
08:55:38 STEP: Performing K8s service preflight check
08:55:38 STEP: Performing Cilium controllers preflight check
08:55:38 STEP: Performing Cilium health check
08:55:38 STEP: Checking whether host EP regenerated
08:55:38 STEP: Performing Cilium status preflight check
08:55:45 STEP: Performing Cilium service preflight check
08:55:45 STEP: Performing K8s service preflight check
08:55:45 STEP: Performing Cilium status preflight check
08:55:45 STEP: Performing Cilium health check
08:55:45 STEP: Performing Cilium controllers preflight check
08:55:45 STEP: Checking whether host EP regenerated
08:55:52 STEP: Performing Cilium service preflight check
08:55:52 STEP: Performing K8s service preflight check
08:55:52 STEP: Performing Cilium controllers preflight check
08:55:52 STEP: Performing Cilium health check
08:55:52 STEP: Checking whether host EP regenerated
08:55:52 STEP: Performing Cilium status preflight check
08:55:59 STEP: Performing Cilium service preflight check
08:55:59 STEP: Performing K8s service preflight check
08:55:59 STEP: Performing Cilium controllers preflight check
08:55:59 STEP: Performing Cilium health check
08:55:59 STEP: Checking whether host EP regenerated
08:55:59 STEP: Performing Cilium status preflight check
08:56:06 STEP: Performing Cilium service preflight check
08:56:06 STEP: Performing K8s service preflight check
08:56:06 STEP: Cilium is not ready yet: connectivity health is failing: cilium-agent 'cilium-5zg7d': connectivity to path 'k8s1.host.primary-address.icmp.status' is unhealthy: 'Connection timed out'
08:56:06 STEP: Performing Cilium status preflight check
08:56:06 STEP: Performing Cilium health check
08:56:06 STEP: Checking whether host EP regenerated
08:56:06 STEP: Performing Cilium controllers preflight check
08:56:13 STEP: Performing Cilium service preflight check
08:56:13 STEP: Performing K8s service preflight check
08:56:13 STEP: Performing Cilium status preflight check
08:56:13 STEP: Performing Cilium health check
08:56:13 STEP: Checking whether host EP regenerated
08:56:13 STEP: Performing Cilium controllers preflight check
08:56:19 STEP: Performing Cilium service preflight check
08:56:19 STEP: Performing K8s service preflight check
08:56:19 STEP: Performing Cilium controllers preflight check
08:56:19 STEP: Performing Cilium health check
08:56:19 STEP: Checking whether host EP regenerated
08:56:19 STEP: Performing Cilium status preflight check
08:56:26 STEP: Performing Cilium service preflight check
08:56:26 STEP: Performing K8s service preflight check
08:56:26 STEP: Performing Cilium controllers preflight check
08:56:26 STEP: Performing Cilium health check
08:56:26 STEP: Checking whether host EP regenerated
08:56:26 STEP: Performing Cilium status preflight check
08:56:33 STEP: Performing Cilium service preflight check
08:56:33 STEP: Performing K8s service preflight check
08:56:33 STEP: Performing Cilium controllers preflight check
08:56:33 STEP: Checking whether host EP regenerated
08:56:33 STEP: Performing Cilium health check
08:56:33 STEP: Performing Cilium status preflight check
08:56:40 STEP: Performing Cilium service preflight check
08:56:40 STEP: Performing K8s service preflight check
08:56:40 STEP: Performing Cilium controllers preflight check
08:56:40 STEP: Performing Cilium status preflight check
08:56:40 STEP: Performing Cilium health check
08:56:40 STEP: Checking whether host EP regenerated
08:56:59 STEP: Performing Cilium service preflight check
08:56:59 STEP: Performing K8s service preflight check
08:56:59 STEP: Cilium is not ready yet: connectivity health is failing: cilium-agent 'cilium-5zg7d': connectivity to path 'k8s1.host.primary-address.icmp.status' is unhealthy: 'Connection timed out'
08:56:59 STEP: Performing Cilium controllers preflight check
08:56:59 STEP: Performing Cilium health check
08:56:59 STEP: Checking whether host EP regenerated
08:56:59 STEP: Performing Cilium status preflight check
08:57:06 STEP: Performing Cilium service preflight check
08:57:06 STEP: Performing K8s service preflight check
08:57:06 STEP: Performing Cilium controllers preflight check
08:57:06 STEP: Performing Cilium health check
08:57:06 STEP: Checking whether host EP regenerated
08:57:06 STEP: Performing Cilium status preflight check
08:57:13 STEP: Performing Cilium service preflight check
08:57:13 STEP: Performing K8s service preflight check
08:57:13 STEP: Performing Cilium controllers preflight check
08:57:13 STEP: Performing Cilium status preflight check
08:57:13 STEP: Performing Cilium health check
08:57:13 STEP: Checking whether host EP regenerated
08:57:20 STEP: Performing Cilium service preflight check
08:57:20 STEP: Performing K8s service preflight check
08:57:20 STEP: Performing Cilium controllers preflight check
08:57:20 STEP: Performing Cilium health check
08:57:20 STEP: Performing Cilium status preflight check
08:57:20 STEP: Checking whether host EP regenerated
08:57:27 STEP: Performing Cilium service preflight check
08:57:27 STEP: Performing K8s service preflight check
08:57:27 STEP: Performing Cilium status preflight check
08:57:27 STEP: Performing Cilium controllers preflight check
08:57:27 STEP: Performing Cilium health check
08:57:27 STEP: Checking whether host EP regenerated
08:57:40 STEP: Performing Cilium service preflight check
08:57:40 STEP: Performing K8s service preflight check
08:57:40 STEP: Performing Cilium controllers preflight check
08:57:40 STEP: Performing Cilium health check
08:57:40 STEP: Checking whether host EP regenerated
08:57:40 STEP: Performing Cilium status preflight check
08:57:47 STEP: Performing Cilium service preflight check
08:57:47 STEP: Performing K8s service preflight check
08:57:47 STEP: Cilium is not ready yet: connectivity health is failing: cilium-agent 'cilium-5zg7d': connectivity to path 'k8s1.host.primary-address.icmp.status' is unhealthy: 'Connection timed out'
08:57:47 STEP: Performing Cilium controllers preflight check
08:57:47 STEP: Performing Cilium status preflight check
08:57:47 STEP: Performing Cilium health check
08:57:47 STEP: Checking whether host EP regenerated
08:57:53 STEP: Performing Cilium service preflight check
08:57:53 STEP: Performing K8s service preflight check
08:57:53 STEP: Performing Cilium controllers preflight check
08:57:53 STEP: Performing Cilium health check
08:57:53 STEP: Checking whether host EP regenerated
08:57:53 STEP: Performing Cilium status preflight check
08:58:00 STEP: Performing Cilium service preflight check
08:58:00 STEP: Performing K8s service preflight check
08:58:00 STEP: Performing Cilium controllers preflight check
08:58:00 STEP: Checking whether host EP regenerated
08:58:00 STEP: Performing Cilium status preflight check
08:58:00 STEP: Performing Cilium health check
08:58:07 STEP: Performing Cilium service preflight check
08:58:07 STEP: Performing K8s service preflight check
08:58:07 STEP: Performing Cilium controllers preflight check
08:58:07 STEP: Performing Cilium status preflight check
08:58:07 STEP: Performing Cilium health check
08:58:07 STEP: Checking whether host EP regenerated
08:58:14 STEP: Performing Cilium service preflight check
08:58:14 STEP: Performing K8s service preflight check
08:58:14 STEP: Performing Cilium controllers preflight check
08:58:14 STEP: Performing Cilium health check
08:58:14 STEP: Performing Cilium status preflight check
08:58:14 STEP: Checking whether host EP regenerated
08:58:21 STEP: Performing Cilium service preflight check
08:58:21 STEP: Performing K8s service preflight check
08:58:24 STEP: Performing Cilium controllers preflight check
08:58:24 STEP: Performing Cilium status preflight check
08:58:24 STEP: Performing Cilium health check
08:58:24 STEP: Checking whether host EP regenerated
08:58:31 STEP: Performing Cilium service preflight check
08:58:31 STEP: Performing K8s service preflight check
08:58:31 STEP: Cilium is not ready yet: connectivity health is failing: cilium-agent 'cilium-5zg7d': connectivity to path 'k8s1.host.primary-address.icmp.status' is unhealthy: 'Connection timed out'
08:58:31 STEP: Performing Cilium status preflight check
08:58:31 STEP: Performing Cilium health check
08:58:31 STEP: Performing Cilium controllers preflight check
08:58:31 STEP: Checking whether host EP regenerated
FAIL: cilium pre-flight checks failed
Expected
<*errors.errorString | 0xc00242d030>: {
s: "Cilium validation failed: 4m0s timeout expired: Last polled error: connectivity health is failing: cilium-agent 'cilium-5zg7d': connectivity to path 'k8s1.host.primary-address.icmp.status' is unhealthy: 'Connection timed out'",
}
to be nil
=== Test Finished at 2023-04-03T08:58:36Z====
08:58:36 STEP: Running JustAfterEach block for EntireTestsuite K8sDatapathConfig
===================== TEST FAILED =====================
08:58:37 STEP: Running AfterFailed block for EntireTestsuite K8sDatapathConfig
08:58:39 STEP: Performing Cilium service preflight check
08:58:39 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-84476dcf4b-fz4bg 0/1 Running 0 37m 10.0.0.198 k8s1 <none> <none>
cilium-monitoring prometheus-7dbb447479-d27j8 1/1 Running 0 37m 10.0.0.184 k8s1 <none> <none>
kube-system cilium-5zg7d 1/1 Running 0 4m40s 192.168.56.12 k8s2 <none> <none>
kube-system cilium-7q4z4 1/1 Running 0 4m40s 192.168.56.11 k8s1 <none> <none>
kube-system cilium-operator-6574d4888c-ls82m 1/1 Running 0 4m40s 192.168.56.11 k8s1 <none> <none>
kube-system cilium-operator-6574d4888c-m8vk9 1/1 Running 0 4m40s 192.168.56.12 k8s2 <none> <none>
kube-system coredns-6b775575b5-hgkt5 1/1 Running 0 4m10s 10.0.0.13 k8s1 <none> <none>
kube-system etcd-k8s1 1/1 Running 0 42m 192.168.56.11 k8s1 <none> <none>
kube-system kube-apiserver-k8s1 1/1 Running 0 42m 192.168.56.11 k8s1 <none> <none>
kube-system kube-controller-manager-k8s1 1/1 Running 0 42m 192.168.56.11 k8s1 <none> <none>
kube-system kube-proxy-vmlzl 1/1 Running 0 38m 192.168.56.12 k8s2 <none> <none>
kube-system kube-proxy-xvhrb 1/1 Running 0 42m 192.168.56.11 k8s1 <none> <none>
kube-system kube-scheduler-k8s1 1/1 Running 0 42m 192.168.56.11 k8s1 <none> <none>
kube-system log-gatherer-mdjx9 1/1 Running 0 37m 192.168.56.11 k8s1 <none> <none>
kube-system log-gatherer-sztmv 1/1 Running 0 37m 192.168.56.12 k8s2 <none> <none>
kube-system registry-adder-njmd9 1/1 Running 0 38m 192.168.56.11 k8s1 <none> <none>
kube-system registry-adder-t667s 1/1 Running 0 38m 192.168.56.12 k8s2 <none> <none>
Stderr:
Fetching command output from pods [cilium-5zg7d cilium-7q4z4]
cmd: kubectl exec -n kube-system cilium-5zg7d -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 (Direct Routing)]
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.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: 21/21 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: 4004/65535 (6.11%), Flows/s: 14.84 Metrics: Disabled
Encryption: Disabled
Cluster health: 1/2 reachable (2023-04-03T08:58:38Z)
Name IP Node Endpoints
k8s1 192.168.56.11 unreachable reachable
Stderr:
cmd: kubectl exec -n kube-system cilium-5zg7d -c cilium-agent -- cilium endpoint list
Exitcode: 0
Stdout:
ENDPOINT POLICY (ingress) POLICY (egress) IDENTITY LABELS (source:key[=value]) IPv6 IPv4 STATUS
ENFORCEMENT ENFORCEMENT
1777 Enabled Enabled 1 k8s:cilium.io/ci-node=k8s2 ready
k8s:status=lockdown
reserved:host
2040 Disabled Disabled 4 reserved:health fd02::1df 10.0.1.201 ready
Stderr:
cmd: kubectl exec -n kube-system cilium-7q4z4 -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 (Direct Routing)]
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.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: 25/25 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: 6913/65535 (10.55%), Flows/s: 25.83 Metrics: Disabled
Encryption: Disabled
Cluster health: 1/2 reachable (2023-04-03T08:58:31Z)
Name IP Node Endpoints
k8s2 192.168.56.12 unreachable reachable
Stderr:
cmd: kubectl exec -n kube-system cilium-7q4z4 -c cilium-agent -- cilium endpoint list
Exitcode: 0
Stdout:
ENDPOINT POLICY (ingress) POLICY (egress) IDENTITY LABELS (source:key[=value]) IPv6 IPv4 STATUS
ENFORCEMENT ENFORCEMENT
1118 Disabled Disabled 4 reserved:health fd02::92 10.0.0.189 ready
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
1649 Disabled Disabled 18097 k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=kube-system fd02::c2 10.0.0.13 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:
===================== Exiting AfterFailed =====================
08:58:48 STEP: Running AfterEach for block EntireTestsuite K8sDatapathConfig
08:58:48 STEP: Running AfterEach for block EntireTestsuite
[[ATTACHMENT|8a16d34d_K8sDatapathConfig_Host_firewall_With_native_routing.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.