forked from docs/doc-exports
Dong, Qiu Jian
86fb05065f
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>
35 lines
5.3 KiB
HTML
35 lines
5.3 KiB
HTML
<a name="cce_faq_00322"></a><a name="cce_faq_00322"></a>
|
|
|
|
<h1 class="topictitle1">Why Does Add-on Installation Fail and Prompt "The release name is already exist"?</h1>
|
|
<div id="body0000001282383800"><div class="section" id="cce_faq_00322__section8233130104816"><h4 class="sectiontitle">Symptom</h4><p id="cce_faq_00322__p1011175916125">When an add-on fails to be installed, the error message "The release name is already exist" is returned.</p>
|
|
</div>
|
|
<p id="cce_faq_00322__p109529175210"></p>
|
|
<div class="section" id="cce_faq_00322__section31161453101314"><h4 class="sectiontitle">Possible Cause</h4><p id="cce_faq_00322__p1184119718145">The add-on release record remains in the Kubernetes cluster. Generally, it is because the cluster etcd has backed up and restored the add-on, or the add-on fails to be installed or deleted.</p>
|
|
</div>
|
|
<div class="section" id="cce_faq_00322__section117635321713"><h4 class="sectiontitle">Solution</h4><p id="cce_faq_00322__p116558397715">Use kubectl to connect to the cluster and manually clear the Secret and Configmap corresponding to add-on release. The following uses autoscaler add-on release as an example.</p>
|
|
</div>
|
|
<ol id="cce_faq_00322__ol184641627123310"><li id="cce_faq_00322__li1391211348275"><span>Connect to the cluster using kubectl, and run the following command to view the Secret list of add-on releases:</span><p><p id="cce_faq_00322__p16721037113115"><strong id="cce_faq_00322__b182761047181016">kubectl get secret -A |grep cceaddon</strong></p>
|
|
<p id="cce_faq_00322__p1910993703118"><span><img id="cce_faq_00322__image1752523483918" src="en-us_image_0000001897904725.png"></span></p>
|
|
<p id="cce_faq_00322__p197451110183214">The Secret name of an add-on release is in the format of <strong id="cce_faq_00322__b118601228123812">sh.helm.release.v1.cceaddon-{<em id="cce_faq_00322__i20853122823820">add-on name</em>}.v*</strong>. If there are multiple release versions, you can delete their Secrets at the same time.</p>
|
|
</p></li><li id="cce_faq_00322__li923191963314"><span>Run the <strong id="cce_faq_00322__b112591511418">release secret</strong> command to delete the Secrets.</span><p><p id="cce_faq_00322__p16231141911331">Example:</p>
|
|
<p id="cce_faq_00322__p1297121313419"><strong id="cce_faq_00322__b2053412209341">kubectl delete secret sh.helm.release.v1.cceaddon-autoscaler.v1 sh.helm.release.v1.cceaddon-autoscaler.v2 -nkube-system</strong></p>
|
|
<p id="cce_faq_00322__p882214523359"><span><img id="cce_faq_00322__image677352084019" src="en-us_image_0000001851744076.png"></span></p>
|
|
</p></li><li id="cce_faq_00322__li84640275332"><span>If the add-on is created when Helm v2 is used, CCE automatically bumps the v2 release in Configmaps to v3 release in Secrets when viewing the add-ons and their details. The v2 release in the original Configmap is not deleted. Run the following command to view the ConfigMap list of add-on releases:</span><p><p id="cce_faq_00322__p636320633419"><strong id="cce_faq_00322__b7463165414713">kubectl get configmap -A | grep cceaddon</strong></p>
|
|
<p id="cce_faq_00322__p43633614343"><span><img id="cce_faq_00322__image1236320673419" src="en-us_image_0000001898024249.png"></span></p>
|
|
<p id="cce_faq_00322__p1336346173411">The ConfigMap name of an add-on release is in the format of <strong id="cce_faq_00322__b194615242309">cceaddon-{<em id="cce_faq_00322__i11760183073010">add-on name</em>}.v*</strong>. If there are multiple release versions, you can delete their ConfigMaps at the same time.</p>
|
|
</p></li><li id="cce_faq_00322__li1223124503314"><span>Run the <strong id="cce_faq_00322__b9757415103719">release configmap</strong> command to delete the ConfigMaps.</span><p><p id="cce_faq_00322__p168812615357">Example:</p>
|
|
<p id="cce_faq_00322__p84007753817"><strong id="cce_faq_00322__b2759481988">kubectl delete configmap cceaddon-autoscaler.v1 cceaddon-autoscaler.v2 -nkube-system</strong></p>
|
|
<p id="cce_faq_00322__p129967483515"><span><img id="cce_faq_00322__image14795155418375" src="en-us_image_0000001851744088.png"></span></p>
|
|
<div class="caution" id="cce_faq_00322__note189615694717"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><p id="cce_faq_00322__p296176154713">Deleting resources in kube-system is a high-risk operation. Ensure that the command is correct before running it to prevent resources from being deleted by mistake.</p>
|
|
</div></div>
|
|
</p></li><li id="cce_faq_00322__li1987732317398"><span>On the CCE console, install add-on and then uninstall it. Ensure that the residual add-on resources are cleared. After the uninstall is complete, install the add-on again.</span><p><div class="note" id="cce_faq_00322__note62786461183"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_faq_00322__p182798467812">When installing the add-on for the first time, you may find it abnormal after the installation due to the residual resources of the previous add-on release, which is normal. In this case, you can uninstall the add-on on the console to ensure that the residual resources are cleared and the add-on can run properly after being installed again.</p>
|
|
</div></div>
|
|
</p></li></ol>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_faq_00215.html">Chart and Add-on</a></div>
|
|
</div>
|
|
</div>
|
|
|