Container Storage Modules Operator: 'Available' Attribute Causes Incorrect Failure Status Report

Résumé: Container Storage Modules Operator: After driver controller down scaling, 'Available' attribute causes incorrect failure status report in deployment.

Cet article concerne Cet article ne concerne pas Cet article n’est associé à aucun produit spécifique. Toutes les versions du produit ne sont pas identifiées dans cet article.
Consulter d’autres ressources

Symptômes

ContainerStorageModule object erroneously reports Status: Failed, when using CSM Operator to downscale deployed CSM components. Check this with the kubectl describe command.

Example:
  1. Scale down existing driver deployment by changing controller count from 2 to 1:
Kubectl scale deploy/driver-controller -n [namespace] –replicas=1
deployment.apps/driver-controller scaled
  1. Get the name of the deployment:
kubectl get deployment -n [namespace]
NAME                         READY   UP-TO-DATE   AVAILABLE   AGE
driver-controller            1/1     1            1           14m
  1. Describe the deployment (shows as failed):
kubectl describe csm -n [namespace] [deployment]
( . . .)
Status:
  Controller Status:
    Available:  2
    Desired:    1
    Failed:     0
  Node Status:
    Available:  2
    Desired:    2
    Failed:     0
  State:        Failed
(. . .)
Despite the Status: Failed in the kubectl describe command output, the down scale of the controller was successful. There is no impact to the functionality of the driver. This is validated by running any of the following commands in Kubernetes after about one hour: 
kubectl get pods -n [namespace]
NAME                READY   STATUS    RESTARTS   AGE
driver-controller   5/5     Running   0          16m
driver-node         2/2     Running   0          16m
driver-node         2/2     Running   0          16m

kubectl get replicaset -n [namespace]
NAME                DESIRED   CURRENT   READY   AGE
driver-controller   1         1         1       17m

kubectl get deployment -n [namespace]
NAME                         READY   UP-TO-DATE   AVAILABLE   AGE
driver-controller            1/1     1            1           24m

Cause

The underlying root cause is a timing issue in the CSM Operator code when requesting the status of the deployment. The code requests a status update from the ContainerStorageModule object before the 'Available' parameter is updated during scale down. This causes a discrepancy between 'Available' and 'Desired' for a short period of time. This discrepancy is reconciled automatically after an hour of time. There is no impact on the functionality of the driver.

Résolution

Workaround:
No workaround is necessary. The 'Available' attribute is updated properly after about one hour and reports the status properly. Driver functionality is not affected at any time.

Produits concernés

Container Storage Modules

Produits

Container Storage Modules Family, Container Storage Modules
Propriétés de l’article
Numéro d’article: 000211555
Type d’article: Solution
Dernière modification: 03 Sep 2025
Version:  5
Trouvez des réponses à vos questions auprès d’autres utilisateurs Dell
Services de support
Vérifiez si votre appareil est couvert par les services de support.