forked from docs/doc-exports
Reviewed-by: Eotvos, Oliver <oliver.eotvos@t-systems.com> Co-authored-by: Dong, Qiu Jian <qiujiandong1@huawei.com> Co-committed-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
27 lines
2.8 KiB
HTML
27 lines
2.8 KiB
HTML
<a name="cce_faq_00210"></a><a name="cce_faq_00210"></a>
|
|
|
|
<h1 class="topictitle1">What Should I Do If Pods in the Terminating State Cannot Be Deleted?</h1>
|
|
<div id="body1570879278266"><div class="section" id="cce_faq_00210__en-us_topic_0197174573_section6692125519183"><h4 class="sectiontitle">Symptom</h4><p id="cce_faq_00210__en-us_topic_0197174573_p17694772510">When a node is in the Unavailable state, CCE migrates container pods on the node and sets the pods running on the node to the <strong id="cce_faq_00210__b1711715311279">Terminating</strong> state.</p>
|
|
<p id="cce_faq_00210__en-us_topic_0197174573_p1273194010258">After the node is restored, the pods in the <strong id="cce_faq_00210__b6694135616278">Terminating</strong> state are automatically deleted.</p>
|
|
<p id="cce_faq_00210__en-us_topic_0197174573_p8421124411235">However, some pods remain in the <strong id="cce_faq_00210__b1326815351254">Terminating</strong> state.</p>
|
|
<pre class="screen" id="cce_faq_00210__screen8662140125515">#kubectl get pod -n aos
|
|
NAME READY STATUS RESTARTS AGE
|
|
aos-apiserver-5f8f5b5585-s9l92 1/1 <strong id="cce_faq_00210__b76681610591">Terminating</strong> 0 3d1h
|
|
aos-cmdbserver-789bf5b497-6rwrg 1/1 Running 0 3d1h
|
|
aos-controller-545d78bs8d-vm6j9 1/1 Running 3 3d1h</pre>
|
|
<p id="cce_faq_00210__en-us_topic_0197174573_p8384100181315">Running <strong id="cce_faq_00210__b211775012011">kubectl delete pods <podname> -n <namespace></strong> cannot delete the pods.</p>
|
|
<pre class="screen" id="cce_faq_00210__en-us_topic_0197174573_screen17720913152418">kubectl delete pods <strong id="cce_faq_00210__b1988613335518">aos-apiserver-5f8f5b5585</strong><strong id="cce_faq_00210__b6758242116">-s9l92</strong> -n aos</pre>
|
|
</div>
|
|
<div class="section" id="cce_faq_00210__en-us_topic_0197174573_section321621711138"><h4 class="sectiontitle">Solution</h4><p id="cce_faq_00210__en-us_topic_0197174573_p1773440172511">You can run the following command to forcibly delete the pods created in any ways:</p>
|
|
<pre class="screen" id="cce_faq_00210__en-us_topic_0197174573_screen1249212552259">kubectl delete pods <strong id="cce_faq_00210__b109754416556"><pod></strong> --grace-period=0 --force</pre>
|
|
<p id="cce_faq_00210__en-us_topic_0197174573_p16291151013272">Therefore, run the following command to delete the pod:</p>
|
|
<pre class="screen" id="cce_faq_00210__en-us_topic_0197174573_screen8759431172716">kubectl delete pods <strong id="cce_faq_00210__b11369930165512">aos-apiserver-5f8f5b5585</strong><strong id="cce_faq_00210__b1277310810117">-s9l92</strong> --grace-period=0 --force</pre>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_faq_00029.html">Workload Abnormalities</a></div>
|
|
</div>
|
|
</div>
|
|
|