forked from docs/doc-exports
Dong, Qiu Jian
6157284549
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>
37 lines
5.3 KiB
HTML
37 lines
5.3 KiB
HTML
<a name="cce_faq_00140"></a><a name="cce_faq_00140"></a>
|
|
|
|
<h1 class="topictitle1">What Should I Do If a Workload Remains in the Creating State?</h1>
|
|
<div id="body1598407111718"><div class="section" id="cce_faq_00140__section145631926125915"><h4 class="sectiontitle">Symptom</h4><p id="cce_faq_00140__p72413220598">The workload remains in the creating state.</p>
|
|
</div>
|
|
<div class="section" id="cce_faq_00140__section7423941175219"><h4 class="sectiontitle">Troubleshooting Process</h4><p id="cce_faq_00140__p17987205213470">The issues here are described in order of how likely they are to occur.</p>
|
|
<p id="cce_faq_00140__p997211345215">Check these causes one by one until you find the cause of the fault.</p>
|
|
<ul id="cce_faq_00140__ul8490384195"><li id="cce_faq_00140__li34912383192"><a href="#cce_faq_00140__section141501505112">Check Item 1: Whether the cce-pause Image Is Deleted by Mistake</a></li><li id="cce_faq_00140__li10595164516190"><a href="#cce_faq_00140__section109321639135910">Check Item 2: Modifying Node Specifications After the CPU Management Policy Is Enabled in the Cluster</a></li></ul>
|
|
</div>
|
|
<div class="section" id="cce_faq_00140__section141501505112"><a name="cce_faq_00140__section141501505112"></a><a name="section141501505112"></a><h4 class="sectiontitle">Check Item 1: Whether the cce-pause Image Is Deleted by Mistake</h4><p id="cce_faq_00140__p10928848192911"><strong id="cce_faq_00140__b14928174822912">Symptom</strong></p>
|
|
<p id="cce_faq_00140__p392812489293">When creating a workload, an error message indicating that the sandbox cannot be created is displayed. This is because the <strong id="cce_faq_00140__b788211466510">cce-pause:3.1</strong> image fails to be pulled.</p>
|
|
<pre class="screen" id="cce_faq_00140__screen1192817481298">Failed to create pod sandbox: rpc error: code = Unknown desc = failed to get sandbox image "cce-pause:3.1": failed to pull image "cce-pause:3.1": failed to pull and unpack image "docker.io/library/cce-pause:3.1": failed to resolve reference "docker.io/library/cce-pause:3.1": pulling from host **** failed with status code [manifests 3.1]: 400 Bad Request</pre>
|
|
<p id="cce_faq_00140__p192912488294"><strong id="cce_faq_00140__b4929144862912">Possible Causes</strong></p>
|
|
<p id="cce_faq_00140__p7929648162920">The image is a system image added during node creation. If the image is deleted by mistake, the workload cannot be created.</p>
|
|
<p id="cce_faq_00140__p59291148102918"><strong id="cce_faq_00140__b1192934812912">Solution</strong></p>
|
|
<ol id="cce_faq_00140__ol498016019356"><li id="cce_faq_00140__li098020153512"><span>Log in to the faulty node.</span></li><li id="cce_faq_00140__li4128105193515"><span>Decompress the cce-pause image installation package.</span><p><pre class="screen" id="cce_faq_00140__screen18162175613419">tar -xzvf /opt/cloud/cce/package/node-package/pause-*.tgz</pre>
|
|
</p></li><li id="cce_faq_00140__li145387163611"><span>Import the image.</span><p><ul id="cce_faq_00140__ul1446723153612"><li id="cce_faq_00140__li20381344173613">Docker nodes:<pre class="screen" id="cce_faq_00140__screen132009517367">docker load -i ./pause/package/image/cce-pause-3.1.tar</pre>
|
|
</li><li id="cce_faq_00140__li1694064733617">containerd nodes:<pre class="screen" id="cce_faq_00140__screen5339459103617">ctr -n k8s.io image import ./pause/package/image/cce-pause-3.1.tar</pre>
|
|
</li></ul>
|
|
</p></li><li id="cce_faq_00140__li11757145853910"><span>Create a workload.</span></li></ol>
|
|
</div>
|
|
<div class="section" id="cce_faq_00140__section109321639135910"><a name="cce_faq_00140__section109321639135910"></a><a name="section109321639135910"></a><h4 class="sectiontitle">Check Item 2: Modifying Node Specifications After the CPU Management Policy Is Enabled in the Cluster</h4><p id="cce_faq_00140__p159869193219">The kubelet option <strong id="cce_faq_00140__b1164243916539">cpu-manager-policy</strong> defaults to <strong id="cce_faq_00140__b5643143911537">static</strong>. This allows granting enhanced CPU affinity and exclusivity to pods with certain resource characteristics on the node. If you modify CCE node specifications on the ECS console, the original CPU information does not match the new CPU information. As a result, workloads on the node cannot be restarted or created.</p>
|
|
<ol id="cce_faq_00140__ol9406433144011"><li id="cce_faq_00140__li9406833184015"><span>Log in to the CCE node (ECS) and delete the <strong id="cce_faq_00140__b17853151217347">cpu_manager_state</strong> file.</span><p><p id="cce_faq_00140__p9637182317014">Example command for deleting the file:</p>
|
|
<pre class="screen" id="cce_faq_00140__screen35921291126">rm -rf /mnt/paas/kubernetes/kubelet/cpu_manager_state</pre>
|
|
</p></li><li id="cce_faq_00140__li124079334408"><span>Restart the node or kubelet. The following is the kubelet restart command:</span><p><pre class="screen" id="cce_faq_00140__screen35579388214">systemctl restart kubelet</pre>
|
|
<p id="cce_faq_00140__p42321938104017">Verify that workloads on the node can be successfully restarted or created.</p>
|
|
<p id="cce_faq_00140__p844124014018">For details, see <a href="cce_faq_00189.html">What Should I Do If I Fail to Restart or Create Workloads on a Node After Modifying the Node Specifications?</a>.</p>
|
|
</p></li></ol>
|
|
</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>
|
|
|