[BUG]: Auto select protocol makes the node driver to crash

[coulof]

Bug Description

After installation of the CSI Driver for PowerMax controller runs ok, but the node drivers loop on:

powermax-node-hwtz9 driver time="2025-01-16T07:27:29Z" level=info msg="/csi.v1.Node/NodeGetInfo: REQ 0010: XXX_NoUnkeyedLiteral={}, XXX_sizecache=0"
powermax-node-hwtz9 driver time="2025-01-16T07:27:29Z" level=error msg="Couldn't find any ip interfaces on any of the port-groups"
powermax-node-hwtz9 driver time="2025-01-16T07:27:29Z" level=error msg="No topology keys could be generated"
powermax-node-hwtz9 driver time="2025-01-16T07:27:29Z" level=info msg="/csi.v1.Node/NodeGetInfo: REP 0010: rpc error: code = FailedPrecondition desc = no topology keys could be generate"
powermax-node-hwtz9 registrar I0116 07:27:29.518532       1 main.go:108] "Received NotifyRegistrationStatus call" status="&RegistrationStatus{PluginRegistered:false,Error:RegisterPlugin error -- plugin registration failed with err: rpc error: code = FailedPrecondition desc = no topology keys could be generate,}"
powermax-node-hwtz9 registrar E0116 07:27:29.518555       1 main.go:110] "Registration process failed with error, restarting registration container" err="RegisterPlugin error -- plugin registration failed with err: rpc error: code = FailedPrecondition desc = no topology keys could be generate"

They do not create the hosts in Unisphere & then crash.

During the first lines of the node log there was was an NVMe error "Couldn't find any ip interfaces on any of the port-groups".

NVMe protocol is not accessible on my lab.

During the deployment, I let X_CSI_TRANSPORT_PROTOCOL: "" per documentation.

After forcing the protocol to X_CSI_TRANSPORT_PROTOCOL: "FC" it passed ok.

The selection protocol seams to be mandatory. So it looks as a regression.

Idk about the implication of forcing a value in case you have multiple storage protocols (e.g. NFS + FC or NVMe + iSCSI).

Logs

Meaningful error message: https://github.com/dell/csi-powermax/blob/c4d17d7dc72a952651cdcca213ceef7a19c04459/service/node.go#L2004

Screenshots

No response

Additional Environment Information

OCP 4.17 on Baremetal
CSM Operator v1.12
Unisphere 10.1
FC connectivity

Steps to Reproduce

Install the driver and do not set X_CSI_TRANSPORT_PROTOCOL ; just like in the sample.

Expected Behavior

X_CSI_TRANSPORT_PROTOCOL: "" must be permitted and pick the available protocol for the node

CSM Driver(s)

PowerMax v2.12

Installation Type

Operator

Container Storage Modules Enabled

No response

Container Orchestrator

Openshift 4.17

Operating System

CoreOS

[csmbot]

@coulof: 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 [email protected].

[francis-nijay]

link: ECS01A-49