Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI: v1.12: Suite-k8s-1.20.K8sServicesTest Checks E/W loadbalancing (ClusterIP, NodePort from inside cluster, etc) with L4 policy Tests NodePort with L4 Policy #30018

Closed
YutaroHayakawa opened this issue Dec 21, 2023 · 6 comments
Labels
area/CI Continuous Integration testing issue or flake ci/flake This is a known failure that occurs in the tree. Please investigate me! stale The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.

Comments

@YutaroHayakawa
Copy link
Member

Test Name

Suite-k8s-1.20.K8sServicesTest Checks E/W loadbalancing (ClusterIP, NodePort from inside cluster, etc) with L4 policy Tests NodePort with L4 Policy

Failure Output

FAIL: Request from testclient-2jng4 pod to service tftp://[fd04::11]:32411/hello failed

Stack Trace

Expected command: kubectl exec -n default testclient-2jng4 -- /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://[fd04::11]:32411/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: exit status 42

Standard Output

Stdout:
 	 
	 Hostname: testds-g4wqz
	 
	 Request Information:
	 	client_address=fd04::11
	 	client_port=18413
	 	real path=/hello
	 	request_scheme=tftp
	 
	 Test round 3799/2 exit code: 0
	 
	 Hostname: testds-ts8fl
	 
	 Request Information:
	 	client_address=fd02::175
	 	client_port=45318
	 	real path=/hello
	 	request_scheme=tftp
	 
	 Test round 3799/3 exit code: 0
	 
	 Hostname: testds-g4wqz
	 
	 Request Information:
	 	client_address=fd04::11
	 	client_port=6535
	 	real path=/hello
	 	request_scheme=tftp
	 
	 Test round 3799/4 exit code: 0
	 
	 Hostname: testds-g4wqz
	 
	 Request Information:
	 	client_address=fd04::11
	 	client_port=28647
	 	real path=/hello
	 	request_scheme=tftp
	 
	 Test round 3799/5 exit code: 0
	 
	 Hostname: testds-g4wqz
	 
	 Request Information:
	 	client_address=fd04::11
	 	client_port=54589
	 	real path=/hello
	 	request_scheme=tftp
	 
	 Test round 3799/6 exit code: 0
	 
	 Hostname: testds-ts8fl
	 
	 Request Information:
	 	client_address=fd02::175
	 	client_port=33226
	 	real path=/hello
	 	request_scheme=tftp
	 
	 Test round 3799/7 exit code: 0
	 
	 Hostname: testds-ts8fl
	 
	 Request Information:
	 	client_address=fd02::175
	 	client_port=44629
	 	real path=/hello
	 	request_scheme=tftp
	 
	 Test round 3799/8 exit code: 0
	 
	 Hostname: testds-g4wqz
	 
	 Request Information:
	 	client_address=fd04::11
	 	client_port=57976
	 	real path=/hello
	 	request_scheme=tftp
	 
	 Test round 3799/9 exit code: 0
	 
	 Hostname: testds-ts8fl
	 
	 Request Information:
	 	client_address=fd02::175
	 	client_port=46368
	 	real path=/hello
	 	request_scheme=tftp
	 
	 Test round 3799/10 exit code: 0
	 failed: :3799/1=71

Standard Error

Stderr:
 	 command terminated with exit code 42

Resources

Anything else?

No response

@YutaroHayakawa YutaroHayakawa added area/CI Continuous Integration testing issue or flake ci/flake This is a known failure that occurs in the tree. Please investigate me! labels Dec 21, 2023
@YutaroHayakawa YutaroHayakawa changed the title CI: Suite-k8s-1.20.K8sServicesTest Checks E/W loadbalancing (ClusterIP, NodePort from inside cluster, etc) with L4 policy Tests NodePort with L4 Policy CI: v1.12: Suite-k8s-1.20.K8sServicesTest Checks E/W loadbalancing (ClusterIP, NodePort from inside cluster, etc) with L4 policy Tests NodePort with L4 Policy Dec 21, 2023
@pippolo84
Copy link
Member

Another hit here

K8sDatapathServicesTest Checks N/S loadbalancing With host policy 
  Tests NodePort

...

FAIL: Request from testclient-hft7g pod to service tftp://[fd00:10:96::3dba]:10069/hello failed
Expected command: kubectl exec -n default testclient-hft7g -- /usr/bin/env 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://[fd00:10:96::3dba]: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: exit status 42
Stdout:
 	 
	 Hostname: testds-mr27t
	 
	 Request Information:
	 	client_address=fd02::e
	 	client_port=36751
	 	real path=/hello
	 	request_scheme=tftp
	 
	 Test round 314/1 exit code: 0
	 
	 Hostname: testds-mr27t
	 
	 Request Information:
	 	client_address=fd02::e
	 	client_port=45577
	 	real path=/hello
	 	request_scheme=tftp
	 
	 Test round 314/2 exit code: 0
	 
	 Hostname: testds-k8pmk
	 
	 Request Information:
	 	client_address=fd02::e
	 	client_port=55441
	 	real path=/hello
	 	request_scheme=tftp
	 
	 Test round 314/3 exit code: 0
	 
	 Hostname: testds-k8pmk
	 
	 Request Information:
	 	client_address=fd02::e
	 	client_port=46686
	 	real path=/hello
	 	request_scheme=tftp
	 
	 Test round 314/4 exit code: 0
	 
	 Hostname: testds-k8pmk
	 
	 Request Information:
	 	client_address=fd02::e
	 	client_port=57444
	 	real path=/hello
	 	request_scheme=tftp
	 
	 Test round 314/5 exit code: 0
	 
	 Hostname: testds-mr27t
	 
	 Request Information:
	 	client_address=fd02::e
	 	client_port=37049
	 	real path=/hello
	 	request_scheme=tftp
	 
	 Test round 314/6 exit code: 0
	 
	 Hostname: testds-mr27t
	 
	 Request Information:
	 	client_address=fd02::e
	 	client_port=[572](https://github.com/cilium/cilium/actions/runs/7384604202/job/20087890519#step:16:574)57
	 	real path=/hello
	 	request_scheme=tftp
	 
	 Test round 314/7 exit code: 0
	 
	 Hostname: testds-mr27t
	 
	 Request Information:
	 	client_address=fd02::e
	 	client_port=33496
	 	real path=/hello
	 	request_scheme=tftp
	 
	 Test round 314/9 exit code: 0
	 
	 Hostname: testds-mr27t
	 
	 Request Information:
	 	client_address=fd02::e
	 	client_port=45600
	 	real path=/hello
	 	request_scheme=tftp
	 
	 Test round 314/10 exit code: 0
	 failed: :314/8=71
	 
Stderr:
 	 command terminated with exit code 42

Full logs
Sysdump

Copy link

github-actions bot commented Mar 4, 2024

This issue has been automatically marked as stale because it has not
had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the stale The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale. label Mar 4, 2024
@github-actions github-actions bot removed the stale The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale. label Mar 9, 2024
@tommyp1ckles
Copy link
Contributor

Hit this here: https://github.com/cilium/cilium/actions/runs/8330407882/job/22795552306, seems to be happening more recently.

The return code (failed: :314/8=71) means that curl is returning with error CURLE_TFTP_ILLEGAL.

Copy link

This issue has been automatically marked as stale because it has not
had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the stale The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale. label May 18, 2024
Copy link

github-actions bot commented Jun 1, 2024

This issue has not seen any activity since it was marked stale.
Closing.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/CI Continuous Integration testing issue or flake ci/flake This is a known failure that occurs in the tree. Please investigate me! stale The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.
Projects
None yet
Development

No branches or pull requests

3 participants