Description

This PR addresses an issue where DataVolumes remain stuck in the ImportScheduled state due to importer pods failing to initialize. The root cause was traced to a failure in the CSI driver's NodeStageVolume operation, which logs:

Warning FailedMapVolume (x8 over 55s) kubelet MapVolume.SetUpDevice failed for volume "techops-f679e8fb01" : rpc error: code = Internal desc = Unable to find device after multiple discovery attempts: at least one NVMe target required

Although NVMeTCP targets from the remote array are successfully discovered and cached, the driver attempts to connect using targets from the local array, resulting in device connection failure.

This update ensures correct target selection during volume staging.

GitHub Issues

List the GitHub issues impacted by this PR:

Checklist:

• Have you run format,vet & lint checks against your submission?
• Have you made sure that the code compiles?
• Did you run the unit & integration tests successfully?
• Have you maintained at least 90% code coverage?
• Have you commented your code, particularly in hard-to-understand areas
• Have you done corresponding changes to the documentation
• Did you run tests in a real Kubernetes cluster?
• Backward compatibility is not broken

How Has This Been Tested?

• Installed PowerMax driver and then Virtualization using a metro SC