CSM Authorization proxy CSM object status stays in a failed state even when pods are successful
Summary: In Container Storage Module (CSM) Operator v1.4.1, the Authorization proxy CSM object status stays in a failed state even when pods are successful.
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 Authorization proxy, resulting in a failed state when pods are successful.
[root@master-1-Zaglt7mQUY8Wg e2e]# kubectl get pods -n authorization NAME READY STATUS RESTARTS AGE authorization-ingress-nginx-controller-58cdf8bb96-b7n8z 1/1 Running 0 84s cert-manager-765754f9cd-w4xg8 1/1 Running 0 85s cert-manager-cainjector-759bbd747b-c5gn8 1/1 Running 0 85s cert-manager-webhook-6fd48c65c8-zks45 1/1 Running 0 85s proxy-server-5755f8cbdd-cb562 3/3 Running 0 87s redis-commander-5475c6469b-qk4qw 1/1 Running 0 87s redis-primary-76c94759c4-7mvph 1/1 Running 0 87s role-service-5c945689cb-snqmv 1/1 Running 0 87s storage-service-56db7c6fbf-fllmp 1/1 Running 0 87s tenant-service-58dd6ff68c-2f6ck 1/1 Running 0 87s [root@master-1-Zaglt7mQUY8Wg e2e]# kubectl get csm -n authorization NAME CREATIONTIME CSIDRIVERTYPE CONFIGVERSION STATE authorization 93s Failed
Cause
Part of the status check logic was looking for a daemonset status, but the auth proxy does not have a daemonset, so the check would fail.
Resolution
Resolution:
Engineering is providing a fix to the status calculation logic in the CSM-Operator v1.4.2 release.
Engineering is providing a fix to the status calculation logic in the CSM-Operator v1.4.2 release.
Products
Container Storage Modules Family, Container Storage ModulesArticle Properties
Article Number: 000222161
Article Type: Solution
Last Modified: 30 Jan 2026
Version: 3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.