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

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

이 문서는 다음에 적용됩니다. 이 문서는 다음에 적용되지 않습니다. 이 문서는 특정 제품과 관련이 없습니다. 모든 제품 버전이 이 문서에 나와 있는 것은 아닙니다.
기타 리소스 확인

증상

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

원인

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.

해결

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.

해당 제품

Container Storage Modules

제품

Container Storage Modules Family, Container Storage Modules
문서 속성
문서 번호: 000211555
문서 유형: Solution
마지막 수정 시간: 03 9월 2025
버전:  5
다른 Dell 사용자에게 질문에 대한 답변 찾기
지원 서비스
디바이스에 지원 서비스가 적용되는지 확인하십시오.