Unsolved
1 Rookie
•
5 Posts
0
24
UnityVsa + CSM-Resiliency: ValidateVolumeHostConnectivity REP 0128: Connected=false
I am testing the UnityVSA to validate some configurations and could successfully mount a PVC using the NFS. When enabling the csm-resiliency, podmon always logs that it can't detect the pod connection to the Array and keeps terminating the pod.
my secret.yaml (as in the example https://github.com/dell/csi-unity/blob/main/samples/secret/secret.yaml)
My test environment is a Linux (Debian 11) k8s cluster running on VirtualBox and the UnityVSA on VMware Workstation. Both VMs can be accessed as they are bridged to host local network. I used the helm charts from https://github.com/dell/helm-charts to setup this environment.
Is there any kind of configuration that could be missing ?
time="2024-05-17T17:35:11Z" level=info runid=124 msg="ValidateVolumeHostConnectivity reply " func="github.com/dell/csi-unity/service.(*service).ValidateVolumeHostConnectivity()" file="/go/src/csi-unity/service/csi_extension_server.go:229"time="2024-05-17T17:35:11Z" level=info msg="/podmon.v1.Podmon/ValidateVolumeHostConnectivity: REP 0124: Connected=false, IosInProgress=false"time="2024-05-17T17:35:11Z" level=info msg="/podmon.v1.Podmon/ValidateVolumeHostConnectivity: REQ 0125: NodeId=controller-0,controller-0, IoSampleTimeSeconds=0"time="2024-05-17T17:35:11Z" level=info runid=125 msg="ValidateVolumeHostConnectivity called node_id:"controller-0,controller-0"" func="github.com/dell/csi-unity/service.(*service).ValidateVolumeHostConnectivity()" file="/go/src/csi-unity/service/csi_extension_server.go:95"time="2024-05-17T17:35:11Z" level=info runid=125 msg="No arrayId passed in, extracting it using other methods" func="github.com/dell/csi-unity/service.(*service).ValidateVolumeHostConnectivity()" file="/go/src/csi-unity/service/csi_extension_server.go:121"time="2024-05-17T17:35:11Z" level=info runid=125 msg="Use default array virt2416byfq7y" func="github.com/dell/csi-unity/service.(*service).ValidateVolumeHostConnectivity()" file="/go/src/csi-unity/service/csi_extension_server.go:138"time="2024-05-17T17:35:11Z" level=info runid=125 msg="Probe of systemID=virt2416byfq7y" func="github.com/dell/csi-unity/service.(*service).ValidateVolumeHostConnectivity()" file="/go/src/csi-unity/service/csi_extension_server.go:148"time="2024-05-17T17:35:11Z" level=info arrayid=virt2416byfq7y runid=125 msg="Checking if array virt2416byfq7y is connected to node controller-0,controller-0" func="github.com/dell/csi-unity/service.(*service).checkIfNodeIsConnected()" file="/go/src/csi-unity/service/csi_extension_server.go:262"my secret.yaml (as in the example https://github.com/dell/csi-unity/blob/main/samples/secret/secret.yaml)
storageArrayList:- arrayId: "VIRT2416BYFQ7Y"username: "admin"password: "admin"endpoint: "https://192.168.31.6/"skipCertificateValidation: trueisDefault: true My test environment is a Linux (Debian 11) k8s cluster running on VirtualBox and the UnityVSA on VMware Workstation. Both VMs can be accessed as they are bridged to host local network. I used the helm charts from https://github.com/dell/helm-charts to setup this environment.
Is there any kind of configuration that could be missing ?
DELL-Josh Cr
Moderator
Moderator
•
8.6K Posts
0
May 23rd, 2024 19:24
Hi,
Thanks for your question.
Is the Unity CSI driver installed? https://dell.to/4bux4ZD
Let us know if you have any additional questions.
Zephyrus3
1 Rookie
1 Rookie
•
5 Posts
0
May 24th, 2024 15:11
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. ..."
DELL-Josh Cr
Moderator
Moderator
•
8.6K Posts
0
May 24th, 2024 17:15
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"
Zephyrus3
1 Rookie
1 Rookie
•
5 Posts
0
May 27th, 2024 13:13
My podmon args are:
(edited)
DELL-Josh Cr
Moderator
Moderator
•
8.6K Posts
0
May 28th, 2024 12:47
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
Zephyrus3
1 Rookie
1 Rookie
•
5 Posts
0
June 11th, 2024 12:43
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.
Zephyrus3
1 Rookie
1 Rookie
•
5 Posts
0
June 11th, 2024 12:57
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.