You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Node(s) CPU architecture, OS, and Version: Linux ali-f-tair-vm-20-26 3.10.0-1160.114.2.el7.x86_64 #1 SMP Wed Mar 20 15:54:52 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration: 1 server, 1 agent
Describe the bug:
To put it simply, the node where the Pod is located is 1.1.1.1. Pinging 1.1.1.1 in the Pod does not work, but pinging any other node such as 1.1.1.2 works.
A new machine with a single network card was added, and the host machine to which the sleep-27 pod request belongs is OK. The GPU machine has multiple network cards, and the host machine to which the sleep pod request belongs is not connected.
The text was updated successfully, but these errors were encountered:
Environmental Info:
K3s Version: v1.24.17-rc2+k3s1 (0d646e4)
Node(s) CPU architecture, OS, and Version: Linux ali-f-tair-vm-20-26 3.10.0-1160.114.2.el7.x86_64 #1 SMP Wed Mar 20 15:54:52 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration: 1 server, 1 agent
Describe the bug:
To put it simply, the node where the Pod is located is 1.1.1.1. Pinging 1.1.1.1 in the Pod does not work, but pinging any other node such as 1.1.1.2 works.
A new machine with a single network card was added, and the host machine to which the sleep-27 pod request belongs is OK. The GPU machine has multiple network cards, and the host machine to which the sleep pod request belongs is not connected.
The text was updated successfully, but these errors were encountered: