Some users are stuck on "pulling image" indefinitely when trying to start up a server.
I think I traced all of the problems to a single node: ip-10-42-3-36.us-west-2.compute.internal
I cordoned off this node so that everyone gets redirected to one of the nodes that's functioning normally. Right now the node just unschedulable. I would like to know what is SOP when I have an issue like this for repairing the node.
Here is the event log, in case it's helpful. I saved some other logs as well.
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 2m default-scheduler Successfully assigned jupyter-sammishi to ip-10-42-3-36.us-west-2.compute.internal
Normal SuccessfulMountVolume 2m kubelet, ip-10-42-3-36.us-west-2.compute.internal MountVolume.SetUp succeeded for volume "nfs-stat312"
Normal SuccessfulMountVolume 2m kubelet, ip-10-42-3-36.us-west-2.compute.internal MountVolume.SetUp succeeded for volume "pv-class-stat312"
Normal Pulling 2m kubelet, ip-10-42-3-36.us-west-2.compute.internal pulling image "jupyterhub/k8s-network-tools:0.7.0"
Some users are stuck on "pulling image" indefinitely when trying to start up a server.
I think I traced all of the problems to a single node: ip-10-42-3-36.us-west-2.compute.internal
I cordoned off this node so that everyone gets redirected to one of the nodes that's functioning normally. Right now the node just unschedulable. I would like to know what is SOP when I have an issue like this for repairing the node.
Here is the event log, in case it's helpful. I saved some other logs as well.