-
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!staleThe stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.
Description
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-K8s/3458/testReport/Suite-k8s-1/13/K8sServicesTest_Checks_service_across_nodes_Tests_NodePort__kube_proxy_/
test_results_Cilium-PR-Ginkgo-Tests-K8s_3458_BDD-Test-k8s-1.13.zip
CI dashboard has a lot of similar failures, but they all seemed to be caused by beforeAll
failures. Note: The CI build (from backport PR #12990) with this failure occurrence had many other tests failing.
Stacktrace
/home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-K8s/1.13-gopath/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:514
Request from testclient-xx9rd pod to service tftp://10.110.178.159:10069/hello failed
Expected command: kubectl exec -n default testclient-xx9rd -- /bin/bash -c 'fails=""; id=$RANDOM; for i in $(seq 1 10); do if curl --path-as-is -s -D /dev/stderr --fail --connect-timeout 5 --max-time 20 tftp://10.110.178.159:10069/hello -H "User-Agent: cilium-test-$id/$i"; then echo "Test round $id/$i exit code: $?"; else fails=$fails:$id/$i=$?; fi; done; if [ -n "$fails" ]; then echo "failed: $fails"; fi; cnt="${fails//[^:]}"; if [ ${#cnt} -gt 0 ]; then exit 42; fi'
To succeed, but it failed:
Exitcode: 42
Err: Process exited with status 42
Stdout:
Hostname: testds-nw5sj
Request Information:
client_address=10.0.1.194
client_port=50720
real path=/hello
request_scheme=tftp
Test round 16035/1 exit code: 0
Hostname: testds-nw5sj
Request Information:
client_address=10.0.1.194
client_port=50048
real path=/hello
request_scheme=tftp
Test round 16035/2 exit code: 0
Hostname: testds-n2h9z
Request Information:
client_address=10.0.1.194
client_port=40414
real path=/hello
request_scheme=tftp
Test round 16035/3 exit code: 0
Hostname: testds-n2h9z
Request Information:
client_address=10.0.1.194
client_port=43850
real path=/hello
request_scheme=tftp
Test round 16035/4 exit code: 0
Hostname: testds-nw5sj
Request Information:
client_address=10.0.1.194
client_port=48103
real path=/hello
request_scheme=tftp
Test round 16035/5 exit code: 0
Hostname: testds-n2h9z
Request Information:
client_address=10.0.1.194
client_port=49876
real path=/hello
request_scheme=tftp
Test round 16035/6 exit code: 0
Hostname: testds-n2h9z
Request Information:
client_address=10.0.1.194
client_port=55372
real path=/hello
request_scheme=tftp
Test round 16035/7 exit code: 0
Hostname: testds-nw5sj
Request Information:
client_address=10.0.1.194
client_port=42358
real path=/hello
request_scheme=tftp
Test round 16035/9 exit code: 0
Hostname: testds-n2h9z
Request Information:
client_address=10.0.1.194
client_port=35092
real path=/hello
request_scheme=tftp
Test round 16035/10 exit code: 0
failed: :16035/8=71
Stderr:
command terminated with exit code 42
/home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-K8s/1.13-gopath/src/github.com/cilium/cilium/test/k8sT/Services.go:736
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
Cilium pods: [cilium-9kcbb cilium-drwpd]
Netpols loaded:
CiliumNetworkPolicies loaded:
Endpoint Policy Enforcement:
Pod Ingress Egress
Cilium agent 'cilium-9kcbb': Status: Ok Health: Ok Nodes "" ContinerRuntime: Kubernetes: Ok KVstore: Ok Controllers: Total 43 Failed 0
Cilium agent 'cilium-drwpd': Status: Ok Health: Ok Nodes "" ContinerRuntime: Kubernetes: Ok KVstore: Ok Controllers: Total 25 Failed 0
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!staleThe stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.