Hi,

Thanks for your question.

Is the Unity CSI driver installed? https://dell.to/4bux4ZD

Let us know if you have any additional questions.

Yes, it is installed. I have already tested that I could provision and mount the PVC using the NFS storage class, and it works. Only when I enable the podmon on csi-unity chart, does this connectivity problem occur.

I don't know if this is related, but on the host's properties, It is always on degraded status and the following message:

"The host does not have any initiators logged into the storage system. ..."

What are the podmon arguments? Should be something like this:

podmon:

   enabled: true

   controller:

     args:

       - "--csisock=unix:/var/run/csi/csi.sock"

       - "--labelvalue=csi-unity"

       - "--driverPath=https://dell.to/4ayFDB9"

       - "--mode=controller"

       - "--skipArrayConnectionValidation=false"

       - "--driver-config-params=/unity-config/driver-config-params.yaml"

       - "--driverPodLabelValue=dell-storage"

       - "--ignoreVolumelessPods=false"

   node:

     args:

       - "--csisock=unix:/var/lib/kubelet/plugins/unity.emc.dell.com/csi_sock"

       - "--labelvalue=csi-unity"

       - "--driverPath=https://dell.to/4ayFDB9"

       - "--mode=node"

       - "--leaderelection=false"

       - "--driver-config-params=/unity-config/driver-config-params.yaml"

       - "--driverPodLabelValue=dell-storage"

       - "--ignoreVolumelessPods=false"

My podmon args are:

podmon:
  # enabled - flag to enable or disable podmon
  # allowed values : boolean
  # defaule value : None
  # Examples : true , false
  enabled: false
  image: docker.io/dellemc/podmon:v1.9.0
  controller:
    args:
      - "--csisock=unix:/var/run/csi/csi.sock"
      - "--labelvalue=csi-unity"
      - "--driverPath=csi-unity.dellemc.com"
      - "--mode=controller"
      - "--skipArrayConnectionValidation=false"
      - "--driver-config-params=/unity-config/driver-config-params.yaml"
      - "--driverPodLabelValue=dell-storage"
      - "--ignoreVolumelessPods=false"
  node:
    args:
      - "--csisock=unix:/var/lib/kubelet/plugins/unity.emc.dell.com/csi_sock"
      - "--labelvalue=csi-unity"
      - "--driverPath=csi-unity.dellemc.com"
      - "--mode=node"
      - "--leaderelection=false"
      - "--driver-config-params=/unity-config/driver-config-params.yaml"
      - "--driverPodLabelValue=dell-storage"
      - "--ignoreVolumelessPods=false"

Those all look fine and the host does not have any initiators is usually a fibre channel error, but I assume since you are doing it virtually you aren’t using FC.

https://dell.to/44XZpFe

Maybe change the logging level to give more information.

PODMON_CONTROLLER_LOG_FORMAT: "text"

   PODMON_CONTROLLER_LOG_LEVEL: "warning"

   PODMON_NODE_LOG_FORMAT: "text"

   PODMON_NODE_LOG_LEVEL: "info"

   PODMON_ARRAY_CONNECTIVITY_POLL_RATE: 20

   PODMON_ARRAY_CONNECTIVITY_CONNECTION_LOSS_THRESHOLD: 2

   PODMON_SKIP_ARRAY_CONNECTION_VALIDATION: true

The use of PODMON_SKIP_ARRAY_CONNECTION_VALIDATION: true seems to have no effect as it still checks for the HostConnectivity and keeps triggering the pod cleanup. 

I could fix the problem with the ValidateVolumeHostConnectivity by adding another interface to the VirtualBox VMs to bridge them to the same network as the UnityVSA VM. With this,  the problems with the initiator paths were fixed and podmon could correctly validate the host connectivity.