<p>Today when I tried to use this command to get the kubernetes deployment rollout status, shows error like this:</p>
<pre><code>&gt; kubectl rollout status deployment/texhub-server-service -n reddwarf-pro
Waiting for deployment spec update to be observed...
</code></pre>
<p>the command stuck and will never end. I also tried to using this command to restart:</p>
<pre><code>kubectl rollout restart deployment/texhub-server-service -n reddwarf-pro
</code></pre>
<p>still stuck when get status. I did not found this deployment was staying busy in console. why did this happen? what should I do to fixed this issue?</p>

Dolphin
<p>As per <strong>Garry Shutler’s</strong> article written on <a href="https://gshutler.com/2018/11/kubernetes-rollout-stuck/" rel="nofollow noreferrer">Kubernetes rollout stuck</a>;</p>
<blockquote>
<p>This seemed to put all replica set creation in limbo as other deployments also ended up stuck in a similar state.</p>
</blockquote>
<blockquote>
<p>Wild speculation is that an in-memory lock was blocking the replica set creation and that killing the process broke the lock.</p>
</blockquote>
<p><strong>Try removing old replica sets, it may help to start work again.</strong>
You can achieve this using the command <code>kubectl delete rs &lt;rs name\&gt;</code>. Where rs name is the name of your ReplicaSet.</p>
<p>You can also refer to other causes for this error in <a href="https://unofficial-kubernetes.readthedocs.io/en/latest/concepts/workloads/controllers/deployment/#failed-deployment" rel="nofollow noreferrer">Failed Deployment</a>;</p>
<blockquote>
<ol>
<li><p>Insufficient quota</p>
</li>
<li><p>Readiness probe failures (ensure your liveness and readiness probes are correctly set)</p>
</li>
<li><p>Image pull errors</p>
</li>
<li><p>Insufficient permissions</p>
</li>
<li><p>Limit ranges</p>
</li>
<li><p>Application runtime misconfiguration</p>
</li>
</ol>
</blockquote>
