[FEATURE]: Driver should allow usage of valid arrays if secret file has combination of valid and invalid arrays.

[sakshi-garg1]

Feature Description

Driver should allow provisioning on valid arrays if secret files has combination of valid and invalid arrays.

When deploying the csi-powerstore driver with some invalid array in the secret file, provisioning fails with 'no available topology found' error, even on valid storage arrays. The 'node' pods for csi-powerstore will enter a crash loop shortly after PVC is created.

Removing the bad entry and redeploying removes the issue. Replacing the bad entry and redeploying brings the issue back, making it highly reproducible. This issue was discovered because an old PowerStore array entry was left in a secret file:

• endpoint: "https://XX.XXX.XX/api/rest"
  globalID: "XXXXXX"
  username:
  password:
  skipCertificateValidation: true
  blockProtocol: "ISCSI"
  nasName: "XXXX"

This behavior might be common across all the drivers e.g. In csi-powerscale when invalid arrays were preset in secret.
Multiple restarts in isilion-controlloer pod

PVC remains in pending state with below events

[csmbot]

@sakshi-garg1: Thank you for submitting this issue!

The issue is currently awaiting triage. Please make sure you have given us as much context as possible.

If the maintainers determine this is a relevant issue, they will remove the needs-triage label and assign an appropriate priority label.

---

We want your feedback! If you have any questions or suggestions regarding our contributing process/workflow, please reach out to us at container.storage.modules@dell.com.