CSM Driver deployment with PowerScale Observability stays in a failed state even when the deployment succeeds.
Summary: In Container Storage Modules (CSM) Operator v1.4.1, the CSM object associated with a driver deployment stays in a failed state even when the deployment succeeds. This occurs with PowerScale Observability. ...
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
The system is unable to correctly display the status of the driver deployment when pods are successful.
[root@master-1-Zaglt7mQUY8Wg csm-operator]# kubectl get pods -n isilon NAME READY STATUS RESTARTS AGE cert-manager-784cdfbc8c-bdgh6 1/1 Running 0 18s cert-manager-cainjector-7b85c5dbdf-bzxll 1/1 Running 0 18s cert-manager-webhook-5f85c69d5c-fkn84 1/1 Running 0 18s isilon-controller-6648cf5f98-92jsr 6/6 Running 0 19s isilon-controller-6648cf5f98-xxtdz 6/6 Running 0 20s isilon-node-lfnc9 2/2 Running 0 20s isilon-node-sll4v 2/2 Running 0 19s [root@master-1-Zaglt7mQUY8Wg csm-operator]# kubectl get csm -n isilon NAME CREATIONTIME CSIDRIVERTYPE CONFIGVERSION STATE isilon 25s isilon v2.9.1 Failed
Cause
An issue in the status check code for observability caused one of the pods not to be found in the code. The PowerScale deployment was referred to by its legacy name Isilon in some places.
Resolution
Resolution:
Engineering has resolved this issue in Operator patch 1.4.2 by updating the name that is checked in the status check to the current name.
Engineering has resolved this issue in Operator patch 1.4.2 by updating the name that is checked in the status check to the current name.
Products
Container Storage Modules Family, Container Storage ModulesArticle Properties
Article Number: 000222165
Article Type: Solution
Last Modified: 03 Sept 2025
Version: 3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.