Normal Customer is running OpenShift 4.18.19 on Azure Red Hat OpenShift (ARO). The cluster uses the managed Azure File CSI driver version v1.30.5, which is subject to the known issue documented upstream:
https://github.com/kubernetes-sigs/azurefile-csi-driver/pull/1694
https://github.com/kubernetes-sigs/azurefile-csi-driver/issues/2569
When VolumeSnapshot operations (manual or Commvault-triggered) occur during Azure API throttling HTTP 429, the CSI driver retries snapshot creation. This results in:
-Multiple duplicate snapshots created on the Azure File Share
-Snapshots that are not visible in Kubernetes
-Snapshot quota exhaustion on the Azure File share
-Backup failures and operational impact
This issue occurs independently of Commvault and is consistently reproducible using native VolumeSnapshot objects.
Customer Impact:
-Customer is unable to perform scheduled production backups
-System accumulates orphaned snapshots
-Storage performance degraded due to repeated retry loops
-Backup compliance risk
Requested Action:
-Backport the fix included in azure-file-csi-driver version 1.30.10+ into the version shipped with OpenShift 4.18
-Provide updated image via the managed CSI driver Operator channels
Justification for Backport:
Customer cannot upgrade to OpenShift 4.19 due to an upcoming change freeze window
Issue directly impacts backup continuity and SLA compliance
Fix is low-risk, localized to retry logic in snapshot creation
Related Bug:
