xs_tcp_setup_socket: connect returned unhandled error -107

[lanss315425]

k8s version: 1.26.13 CHART:nfs-subdir-external-provisioner-4.0.18 APP VERSION :4.0.2

Jul 18 19:08:34 test-c03 kernel: xs_tcp_setup_socket: connect returned unhandled error -107
Jul 18 19:08:37 test-c03 kernel: xs_tcp_setup_socket: connect returned unhandled error -107
Jul 18 19:08:37 test-c03 kernel: xs_tcp_setup_socket: connect returned unhandled error -107
Jul 18 19:08:43 test-c03 kernel: xs_tcp_setup_socket: connect returned unhandled error -107
Jul 18 19:08:46 test-c03 kernel: xs_tcp_setup_socket: connect returned unhandled error -107
Jul 18 19:08:51 test-c03 kernel: xs_tcp_setup_socket: connect returned unhandled error -107
Jul 18 19:08:53 test-c03 kernel: xs_tcp_setup_socket: connect returned unhandled error -107
Jul 18 19:08:55 test-c03 kernel: xs_tcp_setup_socket: connect returned unhandled error -107
Jul 18 19:08:56 test-c03 kernel: xs_tcp_setup_socket: connect returned unhandled error -107
Jul 18 19:09:00 test-c03 kernel: xs_tcp_setup_socket: connect returned unhandled error -107
Jul 18 19:09:00 test-c03 kernel: xs_tcp_setup_socket: connect returned unhandled error -107
Jul 18 19:09:01 test-c03 kernel: xs_tcp_setup_socket: connect returned unhandled error -107
Jul 18 19:09:03 test-c03 kernel: xs_tcp_setup_socket: connect returned unhandled error -107

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten