IBM Cloud Docs
Why can't I log in to my worker nodes or debug them with oc debug command?

Why can't I log in to my worker nodes or debug them with oc debug command?

When you log in to the terminal of worker node or run the oc debug node command from the CLI, you receive the following error.

oc debug node/10.200.0.00
Starting pod/10200000-debug ...

To use host binaries, run chroot /host
Pod IP: 10.200.0.10
If you don't see a command prompt, try pressing enter.

Removing debug pod ...
Error from server: error dialing backend: dial tcp 10.200.0.00:12345: connect: connection timed out

There is a faulty node that is causing DNS issues to the cluster.

To resolve this issue, determine which node is causing the error. Then, stop that node and try running oc debug node. See Debugging clusters.

If you cannot determine which node is causing the issue, reboot your Satellite location control plane hosts one at a time and try running oc debug node. If you are still receiving the error, then reboot one worker node at a time.

If you can determine that a particular worker node is causing the problem and the oc debug node command is successful on other worker nodes, then replace the host where the oc debug node command fails.