<p>I have an AWS EKS cluster (kubernetes version 1.14) which runs JupyterHub application.</p>

<p>One of the users notebook servers is returning a 500 error</p>

<blockquote>
  <p>500 : Internal Server Error 
  Redirect loop detected. Notebook has JupyterHub version unknown (likely &lt; 0.8), but the hub expects 0.9.6. Try installing JupyterHub==0.9.6 in the user environment if you continue to have problems. 
  You can try restarting your server from the homepage.</p>
</blockquote>

<p>Only one user is experiencing this issue, others are not. When I do "kubectl get pod", this users pod shows that it is in state "terminating" (it appears to be stuck in this state).</p>

James Wierzba
<p>I was able to fix it, but I can't say this is the right approach. (I would have preferred to diagnose the root cause)</p>

<ol>
<li>First, I tried deleting the pod <code>kubectl delete pod &lt;pod_name&gt;</code> -- it did not work</li>
<li>Second, I tried force deleting the pod <code>kubectl delete pod &lt;pod_name&gt; --grace-period=0 --force</code> -- it worked, but it turns out this only deletes the handle, the pod resources are then orphaned on the cluster</li>
<li>I checked the node status <code>kubectl get node</code> and noticed one node was stuck in <code>NotReady</code> state. I recycled this node -- still did not work, the user notebook server was still stuck and returning 500 err</li>
<li>Finally, I simply deleted the user notebook server from the jupyter hub admin page. This fixed it....</li>
</ol>
