-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Closed
Labels
area/CIContinuous Integration testing issue or flakeContinuous Integration testing issue or flakeci/flakeThis is a known failure that occurs in the tree. Please investigate me!This is a known failure that occurs in the tree. Please investigate me!
Description
Test Name
Suite-k8s-1.26.K8sDatapathServicesTest Checks N/S loadbalancing With host policy Tests NodePort
Failure Output
•! Panic in Spec Setup (BeforeEach) [161.815 seconds]
Stack Trace
/home/jenkins/workspace/cilium-v1.13-k8s-1.26-kernel-net-next/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:453
Test Panicked
/home/jenkins/workspace/cilium-v1.13-k8s-1.26-kernel-net-next/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:443
Standard 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
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
Cilium pods: [cilium-k5stk cilium-xhrww]
Netpols loaded:
CiliumNetworkPolicies loaded:
Endpoint Policy Enforcement:
Pod Ingress Egress
app1-5989697f89-29g9l false false
app2-7fd4ddfc6-wmqg6 false false
echo-7945986bb5-fjqwc false false
echo-7945986bb5-md8wm false false
testds-vxx7b false false
coredns-6d97d5ddb-m4m8h false false
prometheus-8c7df94b4-z6gb8 false false
app1-5989697f89-vztc5 false false
app3-d5f4b5fb5-796ts false false
testds-fgq7h false false
grafana-67ff49cd99-lhzx2 false false
test-k8s2-76f4bdcf49-8d5jv false false
testclient-2wf7d false false
testclient-l58wn false false
Cilium agent 'cilium-k5stk': Status: Ok Health: Ok Nodes "" ContainerRuntime: Kubernetes: Ok KVstore: Ok Controllers: Total 39 Failed 0
Cilium agent 'cilium-xhrww': Status: Ok Health: Ok Nodes "" ContainerRuntime: Kubernetes: Ok KVstore: Ok Controllers: Total 69 Failed 0
Standard Error
06:28:19 STEP: Running BeforeAll block for EntireTestsuite K8sDatapathServicesTest Checks N/S loadbalancing With host policy
06:28:19 STEP: Installing Cilium
06:28:21 STEP: Waiting for Cilium to become ready
06:28:42 STEP: Validating if Kubernetes DNS is deployed
06:28:42 STEP: Checking if deployment is ready
06:28:42 STEP: Checking if kube-dns service is plumbed correctly
06:28:42 STEP: Checking if pods have identity
06:28:42 STEP: Checking if DNS can resolve
06:28:47 STEP: Kubernetes DNS is up and operational
06:28:47 STEP: Validating Cilium Installation
06:28:47 STEP: Performing Cilium controllers preflight check
06:28:47 STEP: Performing Cilium status preflight check
06:28:47 STEP: Performing Cilium health check
06:28:47 STEP: Checking whether host EP regenerated
06:28:57 STEP: Performing Cilium service preflight check
06:28:57 STEP: Performing K8s service preflight check
06:28:57 STEP: Cilium is not ready yet: host EP is not ready: cilium-agent "cilium-k5stk" host EP is not in ready state: "regenerating"
06:28:57 STEP: Performing Cilium controllers preflight check
06:28:57 STEP: Performing Cilium status preflight check
06:28:57 STEP: Checking whether host EP regenerated
06:28:57 STEP: Performing Cilium health check
06:29:06 STEP: Performing Cilium service preflight check
06:29:06 STEP: Performing K8s service preflight check
06:29:10 STEP: Performing Cilium controllers preflight check
06:29:10 STEP: Checking whether host EP regenerated
06:29:10 STEP: Performing Cilium status preflight check
06:29:10 STEP: Performing Cilium health check
06:29:19 STEP: Performing Cilium service preflight check
06:29:19 STEP: Performing K8s service preflight check
06:29:23 STEP: Waiting for cilium-operator to be ready
06:29:23 STEP: WaitforPods(namespace="kube-system", filter="-l name=cilium-operator")
06:29:23 STEP: WaitforPods(namespace="kube-system", filter="-l name=cilium-operator") => <nil>
06:29:23 STEP: Running JustAfterEach block for EntireTestsuite K8sDatapathServicesTest
===================== TEST FAILED =====================
06:29:24 STEP: Running AfterFailed block for EntireTestsuite K8sDatapathServicesTest
<Truncated, too long, Please view full console log below>
06:29:51 STEP: Installing Cilium
06:29:53 STEP: Waiting for Cilium to become ready
06:30:14 STEP: Validating if Kubernetes DNS is deployed
06:30:14 STEP: Checking if deployment is ready
06:30:15 STEP: Checking if kube-dns service is plumbed correctly
06:30:15 STEP: Checking if pods have identity
06:30:15 STEP: Checking if DNS can resolve
06:30:19 STEP: Kubernetes DNS is up and operational
06:30:19 STEP: Validating Cilium Installation
06:30:19 STEP: Performing Cilium controllers preflight check
06:30:19 STEP: Performing Cilium health check
06:30:19 STEP: Performing Cilium status preflight check
06:30:19 STEP: Checking whether host EP regenerated
06:30:29 STEP: Performing Cilium service preflight check
06:30:29 STEP: Performing K8s service preflight check
06:30:29 STEP: Cilium is not ready yet: host EP is not ready: cilium-agent "cilium-mdgcn" host EP is not in ready state: "restoring"
06:30:29 STEP: Performing Cilium controllers preflight check
06:30:29 STEP: Performing Cilium health check
06:30:29 STEP: Performing Cilium status preflight check
06:30:29 STEP: Checking whether host EP regenerated
06:30:39 STEP: Performing Cilium service preflight check
06:30:39 STEP: Performing K8s service preflight check
06:30:47 STEP: Cilium is not ready yet: host EP is not ready: cilium-agent "cilium-mdgcn" host EP is not in ready state: "regenerating"
06:30:47 STEP: Performing Cilium controllers preflight check
06:30:47 STEP: Performing Cilium health check
06:30:47 STEP: Performing Cilium status preflight check
06:30:47 STEP: Checking whether host EP regenerated
06:30:56 STEP: Performing Cilium service preflight check
06:30:56 STEP: Performing K8s service preflight check
06:31:00 STEP: Waiting for cilium-operator to be ready
06:31:00 STEP: WaitforPods(namespace="kube-system", filter="-l name=cilium-operator")
06:31:01 STEP: WaitforPods(namespace="kube-system", filter="-l name=cilium-operator") => <nil>
Resources
- Jenkins URL: https://jenkins.cilium.io/view/Cilium-v1.13/job/cilium-v1.13-k8s-1.26-kernel-net-next/11/testReport/Suite-k8s-1/26/K8sDatapathServicesTest_Checks_N_S_loadbalancing_With_host_policy_Tests_NodePort/
- ZIP file(s): https://jenkins.cilium.io/view/Cilium-v1.13/job/cilium-v1.13-k8s-1.26-kernel-net-next/11/testReport/Suite-k8s-1/26/K8sDatapathServicesTest_Checks_N_S_loadbalancing_With_host_policy_Tests_NodePort/attachments/e1145bc1_K8sDatapathServicesTest_Checks_N-S_loadbalancing_With_host_policy_Tests_NodePort.zip
Unable to upload zip file to issue directly, as the file is too big (35MB > limit of 25MB)
Anything else?
00:31:01 •! Panic in Spec Setup (BeforeEach) [161.815 seconds]
00:31:01 K8sDatapathServicesTest
00:31:01 /home/jenkins/workspace/cilium-v1.13-k8s-1.26-kernel-net-next/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:461
00:31:01 Checks N/S loadbalancing
00:31:01 /home/jenkins/workspace/cilium-v1.13-k8s-1.26-kernel-net-next/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:461
00:31:01 With host policy
00:31:01 /home/jenkins/workspace/cilium-v1.13-k8s-1.26-kernel-net-next/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:461
00:31:01 Tests NodePort [BeforeEach]
00:31:01 /home/jenkins/workspace/cilium-v1.13-k8s-1.26-kernel-net-next/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:515
00:31:01
00:31:01 Test Panicked
00:31:01 runtime error: invalid memory address or nil pointer dereference
00:31:01 /home/jenkins/workspace/cilium-v1.13-k8s-1.26-kernel-net-next/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:443
00:31:01
00:31:01 Full Stack Trace
00:31:01 github.com/cilium/cilium/test/ginkgo-ext.beforeEach.func1.1()
00:31:01 /home/jenkins/workspace/cilium-v1.13-k8s-1.26-kernel-net-next/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:443 +0x47
00:31:01 panic({0x20dcbc0, 0x3acecf0})
00:31:01 /usr/local/go/src/runtime/panic.go:884 +0x213
00:31:01 github.com/cilium/cilium/test/k8s.DeployCiliumOptionsAndDNS(0x0, {0xc0009ea140?, 0x279e201?}, 0xc0031fecd0?)
00:31:01 /home/jenkins/workspace/cilium-v1.13-k8s-1.26-kernel-net-next/src/github.com/cilium/cilium/test/k8s/assertion_helpers.go:204 +0x27
00:31:01 github.com/cilium/cilium/test/helpers.(*DeploymentManager).DeployCilium(0x3b22dc0, 0xc0005f3800?, 0x247d0a1?)
00:31:01 /home/jenkins/workspace/cilium-v1.13-k8s-1.26-kernel-net-next/src/github.com/cilium/cilium/test/helpers/manifest.go:305 +0x3c
00:31:01 github.com/cilium/cilium/test/k8s.prepareHostPolicyEnforcement(0xc0005f32c0)
00:31:01 /home/jenkins/workspace/cilium-v1.13-k8s-1.26-kernel-net-next/src/github.com/cilium/cilium/test/k8s/datapath_configuration.go:548 +0xa5
00:31:01 github.com/cilium/cilium/test/k8s.glob..func22.7.21.1()
00:31:01 /home/jenkins/workspace/cilium-v1.13-k8s-1.26-kernel-net-next/src/github.com/cilium/cilium/test/k8s/services.go:589 +0xb2
00:31:01 github.com/cilium/cilium/test/ginkgo-ext.BeforeAll.func1()
00:31:01 /home/jenkins/workspace/cilium-v1.13-k8s-1.26-kernel-net-next/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:195 +0x69
00:31:01 github.com/cilium/cilium/test/ginkgo-ext.beforeEach.func1()
00:31:01 /home/jenkins/workspace/cilium-v1.13-k8s-1.26-kernel-net-next/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:447 +0xe6
00:31:01 github.com/cilium/cilium/test/ginkgo-ext.applyAdvice.func1({0x3b548a8, 0x0, 0x0})
00:31:01 /home/jenkins/workspace/cilium-v1.13-k8s-1.26-kernel-net-next/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:558 +0x8a
00:31:01 github.com/cilium/cilium/test.Test(0xc00046ad00)
00:31:01 /home/jenkins/workspace/cilium-v1.13-k8s-1.26-kernel-net-next/src/github.com/cilium/cilium/test/test_suite_test.go:112 +0x484
00:31:01 testing.tRunner(0xc00046ad00, 0x2597978)
00:31:01 /usr/local/go/src/testing/testing.go:1576 +0x10b
00:31:01 created by testing.(*T).Run
00:31:01 /usr/local/go/src/testing/testing.go:1629 +0x3ea
Jenkins does not include the panic in the given stdout/stderr. The above logs can be found in the full console log at https://jenkins.cilium.io/view/Cilium-v1.13/job/cilium-v1.13-k8s-1.26-kernel-net-next/11/consoleFull.
Related failure message for the test:
FAIL: Policy cannot be deleted
tommyp1ckles
Metadata
Metadata
Assignees
Labels
area/CIContinuous Integration testing issue or flakeContinuous Integration testing issue or flakeci/flakeThis is a known failure that occurs in the tree. Please investigate me!This is a known failure that occurs in the tree. Please investigate me!