<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Huawei CSI Service Issues on Huawei</title><link>https://huawei.github.io/css-docs/en/v4.11.0/troubleshooting/huawei-csi-service-issues/</link><description>Recent content in Huawei CSI Service Issues on Huawei</description><generator>Hugo</generator><language>en</language><copyright>Copyright © 2025 Huawei Technologies Co., Ltd. All rights reserved.</copyright><atom:link href="https://huawei.github.io/css-docs/en/v4.11.0/troubleshooting/huawei-csi-service-issues/index.xml" rel="self" type="application/rss+xml"/><item><title>Failed to Start the huawei-csi-node Service with Error Message "/var/lib/iscsi is not a directory" Reported</title><link>https://huawei.github.io/css-docs/en/v4.11.0/troubleshooting/huawei-csi-service-issues/failed-to-start-the-huawei-csi-node-service-with-error-message-var-lib-iscsi-is-not-a-directory-repo/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://huawei.github.io/css-docs/en/v4.11.0/troubleshooting/huawei-csi-service-issues/failed-to-start-the-huawei-csi-node-service-with-error-message-var-lib-iscsi-is-not-a-directory-repo/</guid><description>&lt;h2 id="en-us_topic_0000001086137838_section1566717121452">Symptom&lt;/h2>
&lt;p>The huawei-csi-node service cannot be started. When you run the &lt;strong>kubectl describe daemonset huawei-csi-node -n huawei-csi&lt;/strong> command, error message &amp;ldquo;/var/lib/iscsi is not a directory&amp;rdquo; is reported.&lt;/p>
&lt;h2 id="en-us_topic_0000001086137838_section1425013451056">Root Cause Analysis&lt;/h2>
&lt;p>The &lt;strong>/var/lib/iscsi&lt;/strong> directory does not exist in the huawei-csi-node container.&lt;/p>
&lt;h2 id="en-us_topic_0000001086137838_section350653016492">Solution or Workaround&lt;/h2>
&lt;ol>
&lt;li>
&lt;p>Use a remote access tool, such as PuTTY, to log in to any master node in the Kubernetes cluster through the management IP address.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Go to the directory where the Helm project is located. If the previous Helm project cannot be found, copy the &lt;strong>helm&lt;/strong> directory in the component package to any directory on the master node. For details about the component package path, see 
&lt;a href="https://huawei.github.io/css-docs/css-docs/en/docs/installation-and-deployment/csi/installation-preparations/downloading-the-huawei-csi-software-package/#en-us_topic_0150885197_table17200162435412">Table 1&lt;/a>
.&lt;/p></description></item><item><title>Huawei CSI Services Fail to Be Started and Error Message "/etc/localtime is not a file" Is Displayed</title><link>https://huawei.github.io/css-docs/en/v4.11.0/troubleshooting/huawei-csi-service-issues/huawei-csi-services-fail-to-be-started-and-error-message-etc-localtime-is-not-a-file-is-displayed/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://huawei.github.io/css-docs/en/v4.11.0/troubleshooting/huawei-csi-service-issues/huawei-csi-services-fail-to-be-started-and-error-message-etc-localtime-is-not-a-file-is-displayed/</guid><description>&lt;h2 id="en-us_topic_0000001086137838_section1566717121452">Symptom&lt;/h2>
&lt;p>During the installation and deployment of CSI, a Pod fails to run and is in the &lt;strong>ContainerCreating&lt;/strong> state. Alarm &lt;strong>/etc/localtime is not a file&lt;/strong> is generated for the Pod.&lt;/p>
&lt;h2 id="en-us_topic_0000001086137838_section1425013451056">Root Cause Analysis&lt;/h2>
&lt;p>When the container mounts the &lt;strong>/etc/localtime&lt;/strong> file on the host, the type is incorrectly identified. As a result, the container fails to mount the &lt;strong>/etc/localtime&lt;/strong> file on the host and the Pod cannot run.&lt;/p>
&lt;h2 id="section158611659145513">Procedure&lt;/h2>
&lt;ol>
&lt;li>
&lt;p>Use a remote access tool, such as PuTTY, to log in to any master node in the Kubernetes cluster through the management IP address.&lt;/p></description></item><item><title>Failed to Start huawei-csi Services with the Status Displayed as InvalidImageName</title><link>https://huawei.github.io/css-docs/en/v4.11.0/troubleshooting/huawei-csi-service-issues/failed-to-start-huawei-csi-services-with-the-status-displayed-as-invalidimagename/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://huawei.github.io/css-docs/en/v4.11.0/troubleshooting/huawei-csi-service-issues/failed-to-start-huawei-csi-services-with-the-status-displayed-as-invalidimagename/</guid><description>&lt;h2 id="en-us_topic_0000001205368783_section1566717121452">Symptom&lt;/h2>
&lt;p>The huawei-csi services (huawei-csi-controller or huawei-csi-node) cannot be started. After the &lt;strong>kubectl get pod -A | grep huawei&lt;/strong> command is executed, the command output shows that the service status is &lt;strong>InvalidImageName&lt;/strong>.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#4c4f69;background-color:#eff1f5;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-fallback" data-lang="fallback">&lt;span style="display:flex;">&lt;span>kubectl get pod -A | grep huawei
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>The following is an example of the command output.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#4c4f69;background-color:#eff1f5;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-fallback" data-lang="fallback">&lt;span style="display:flex;">&lt;span>huawei-csi huawei-csi-controller-fd5f97768-qlldc 6/9 InvalidImageName 0 16s
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>huawei-csi huawei-csi-node-25txd 2/3 InvalidImageName 0 15s
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="en-us_topic_0000001205368783_section1425013451056">Root Cause Analysis&lt;/h2>
&lt;p>In the .yaml configuration files of the controller and node, the Huawei CSI image version number is incorrect. For example:&lt;/p></description></item></channel></rss>