[BUG]: CSI-PowerFlex: SDC Rename fails when configuring multiple arrays in the secret

[OA72280]

Bug Description

When installing the PowerFlex CSI with the CSM Operator 1.3 and when enabling the sdc rename

    # X_CSI_RENAME_SDC_ENABLED: Enable/Disable rename of SDC
    # Allowed values:
    #   true: enable renaming
    #   false: disable renaming
    # Default value: false
    - name: X_CSI_RENAME_SDC_ENABLED
      value: "true"
      
     And specifically where using multiple PowerFlex systems, only one system registers the SDC's being named that of their respective worker node. 
     
     Here is the secret format for both 

• username: "admin"
  password: "redacted"
  systemID: "098cb5redacted"
  endpoint: "https://redacted"
  skipCertificateValidation: true
  isDefault: true
  mdm: "192.168.155.254,192.168.156.254"

• username: "admin"
  password: "redacted"
  systemID: "d5a63e7redacted"
  endpoint: "https://redacted"
  skipCertificateValidation: true
  isDefault: false
  mdm: "192.168.151.254,192.168.152.254"

  Is it necessary to have the system names variable?

Logs

None

Screenshots

No response

Additional Environment Information

No response

Steps to Reproduce

n/a

Expected Behavior

Expected to see the SDCs renamed by their worker node name from each powerflex system. Only one system shows the names of their respective SDC's successfully updated.

CSM Driver(s)

CSM 1.3 from Operator Hub on OpenShift 4.12

Installation Type

Operator

Container Storage Modules Enabled

No response

Container Orchestrator

n/a

Operating System

RHCOS

[csmbot]

@OA72280: 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 respond appropriately.

---

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.

[OA72280]

Re-attempted to deploy with an updated secret that includes the allSystemNames - same result as outlined in initial bug

[bharathsreekanth]

@VamsiSiddu-7 Can you create a defect for this internally and assign it to the team? Thanks.

[gallacher]

/sync

[csmbot]

link: 18734

[suryagupta4]

Hi @OA72280, can you please provide node pod logs from all the worker nodes for the driver container? As per the implementation, renameSDC method iterates over the connectedSystemID list which contains all the systemID's for renaming. It would be clear from the logs whether the systemID's are fetched correctly or not.
Ref: https://github.com/dell/csi-powerflex/blob/main/service/node.go#L573

Thanks.

[suryagupta4]

Hi @OA72280, can you please provide the required logs for this? Thank you.

[OA72280]

The environment is no longer available / so the description is all that is available in what occurred Thank you

…

On Thu, Nov 2, 2023 at 1:01 AM Surya Gupta ***@***.***> wrote: Hi @OA72280 <https://github.com/OA72280>, can you please provide the required logs for this? Thank you. — Reply to this email directly, view it on GitHub <#1020 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFRJVRSTOAFIFJNU4ZP6KR3YCMSK3AVCNFSM6AAAAAA6PTMNIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJQGA3TCNJVGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[suryagupta4]

@OA72280 Thanks for the response. We tested in one of our environment and found that the SDC was getting renamed for both of the systems configured that is why we wanted to have a look at the logs. If you get hold of another environment, please give it a try and provide us the logs if similar issue persist. Thank you.