DELL Technologies

registration container failed The node [nodeb] is not added to any of the arrays

Hi Experts, I'm running Test Unity CSI Driver, trying to mount a iSCSI volume to the mysql container. After created the storageclass, PVC, PV. The registration container failed on the worker node. It's keep reporting "The node [nodeb] is not added to any of the arrays" Any idea what that m

1.1K

3

0

registration container failed The node [nodeb] is not added to any of the arrays

Hi Experts, I'm running Test Unity CSI Driver, trying to mount a iSCSI volume to the mysql container. After created the storageclass, PVC, PV. The registration container failed on the worker node. It's keep reporting "The node [nodeb] is not added to any of the arrays" Any idea what that m

adding my sample-test.yaml file: [root@master test]# cat sample-pvol1.jsonapiVersion: v1kind: Namespacemetadata:name: test-unity---kind: PersistentVolumeClaimapiVersion: v1metadata:name: pvol1namespace: test-unityspec:accessModes:- ReadWriteOncevolu

registration container failed The node [nodeb] is not added to any of the arrays

Hi Experts, I'm running Test Unity CSI Driver, trying to mount a iSCSI volume to the mysql container. After created the storageclass, PVC, PV. The registration container failed on the worker node. It's keep reporting "The node [nodeb] is not added to any of the arrays" Any idea what that m

Here is the registration container log :

Unity CSI driver not creating volume on Unity

Hi Gurus, - I'm setting up kubernetes cluster, and following https://dell.github.io/storage-plugin-docs/docs/installation/helm/unity/, to install CSI driver for unity. - I'm able to get the pods running: [root@master test]# kubectl get po -n unityNAME READY STATUS RESTARTS AGEsnapshot-contro

yes. It's stupid, but I was not realizing it's harmful.

Unity CSI driver not creating volume on Unity

Hi Gurus, - I'm setting up kubernetes cluster, and following https://dell.github.io/storage-plugin-docs/docs/installation/helm/unity/, to install CSI driver for unity. - I'm able to get the pods running: [root@master test]# kubectl get po -n unityNAME READY STATUS RESTARTS AGEsnapshot-contro

Thanks a lot to bring the volumeBindMode to me. Back to Unity CSI driver version 1.2.0, I was not aware of this parameter, and from the note I had before, seems it was default "immediate", because right after create the PVC, I was able to verify the

Unity CSI driver not creating volume on Unity

Hi Gurus, - I'm setting up kubernetes cluster, and following https://dell.github.io/storage-plugin-docs/docs/installation/helm/unity/, to install CSI driver for unity. - I'm able to get the pods running: [root@master test]# kubectl get po -n unityNAME READY STATUS RESTARTS AGEsnapshot-contro

1.9K

6

0

MountVolume.MountDevice failed for volume

Hi Experts, I'm deploying a pod on Unity storage using iSCSI protocol. I have the pvc created, and volume looks good on Unity side. [root@master helm]# kubectl get pvcNAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGEtest-iscsi-vol-claim Bound jij8-csivol-369833ea70 10Gi RWO unity-is

Bingo! It's the host was not able initiator rescan was not working, and the lsblk was not displaying anything. I actually did reboot the worker, it thought it was going to do a re-scan, just to save time. But I got pay back on this. After I can the

MountVolume.MountDevice failed for volume

Hi Experts, I'm deploying a pod on Unity storage using iSCSI protocol. I have the pvc created, and volume looks good on Unity side. [root@master helm]# kubectl get pvcNAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGEtest-iscsi-vol-claim Bound jij8-csivol-369833ea70 10Gi RWO unity-is

Hi, Yes, I can confirm that on array side, once I created the pvc, the new storage lun can be created ok, and presenting to the worker node. The worker node iSCSI session is also looking fine. Paths are showing active on Storage Unisphere as wel

MountVolume.MountDevice failed for volume

Hi Experts, I'm deploying a pod on Unity storage using iSCSI protocol. I have the pvc created, and volume looks good on Unity side. [root@master helm]# kubectl get pvcNAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGEtest-iscsi-vol-claim Bound jij8-csivol-369833ea70 10Gi RWO unity-is

18.7K

4

0

Failed to install CSI 1.2.0 driver for Unity

Experts, I'm trying to install CSI 1.2.0 on centOS k8s cluster, but failed. From the controller pod, seems there's authentication issue. Could you please share any idea on this? Here's my secret.json file: [root@master helm]# cat secret.json{ "storageArrayList": [{ "username": " ", "password":

You are genius! It's working now, and I can continue my test. FYI, when I was working on v1.1.0, I was able to install the CSI by specifying the username/password encoded in base64 in myvalue file. Reading a few online doc regarding the secret, it s

143033

About me

143033 has won 2 Badges (View Badges)

143033's Activities

143033

registration container failed The node [nodeb] is not added to any of the arrays

143033

143033

registration container failed The node [nodeb] is not added to any of the arrays

143033

143033

registration container failed The node [nodeb] is not added to any of the arrays

143033

143033

Unity CSI driver not creating volume on Unity

143033

143033

Unity CSI driver not creating volume on Unity

143033

Unity CSI driver not creating volume on Unity

143033

143033

MountVolume.MountDevice failed for volume

143033

143033

MountVolume.MountDevice failed for volume

143033

MountVolume.MountDevice failed for volume

143033

143033

Failed to install CSI 1.2.0 driver for Unity

Engagement Stats

Member Stats

My Photos