Unity CSI CSI integration with Kubertness

We have received an chat for the below issue: As we have never worked on this prior, requesting your assistance in below customer query:

Objective and Overview

Use the EMC CSI integration for Kubernetes to auto provision storage on the EMC Unity SANs as and when PODS are created, access to the SAN is done using Fibre Channel with all hosts zoned. Platform is operating K8S 1.21.0 on Centos 7 running on Hyper-V and Virtual Fibre Channel adapters. Deployment of the CSI has been completed without issue using the EMC guides.

Issues

• Test pod, using sample.yaml, is created as expected
• The SAN shows LUN created and node running the POD is granted access
• POD fails to come online as the error ‘failed to read port_name for FC target: open /sys/class/fc_transport/targetX:0:0/port_name: no such file or directory’ where ‘X’ is 1 or 2
• Checking the directory on the Kubernetes Node I can clearly see that port_name does not exist

• Yet if I look in /sys/class/fc_host/hostX (1 or 2) on the same Kubernetes Node the file is present

If I check a physical server I see that /sys/class/fc_transport/targetX:0:0/port_name is present, so the issue seems to be down to a difference between the usage of physical and virtual fibre channel and the path that the CSI is using to read the WWN value from port_name.

Awaiting your response.