#Trident on MetroCluster issue

1 messages · Page 1 of 1 (latest)

azure badger
#

Hello, dear all.
Maybe someone can help. We're trying to setup the trident with ONTAP 9.8 Metro cluster cluster. We have a dedicated StorageClass for that and a dedicated backend was set up. We're getting this error on PVC, when trying to deploy a test pod with a mounted PVC. If we apply the same deployment to the regular NAS based StorageClass, all is working well.

Name:          pvc-test
Namespace:     test
StorageClass:  test
Status:        Pending
Volume:
Labels:        <none>
Annotations:   volume.beta.kubernetes.io/storage-provisioner: csi.trident.netapp.io
               volume.kubernetes.io/selected-node: test01
               volume.kubernetes.io/storage-provisioner: csi.trident.netapp.io
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Used By:       app-pod-1
Events:
  Type    Reason                Age                   From                         Message
  ----    ------                ----                  ----                         -------
  Normal  ExternalProvisioning  49s (x521 over 130m)  persistentvolume-controller  waiting for a volume to be created, either by
external provisioner "csi.trident.netapp.io" or manually created by system administrator

On the NetApp itself, the volume is created, regardless that the error is saying its waiting for a volume to be created.

Thanks a lot in advance.

torpid forum
#

What's the name of the volume that is getting created?

azure badger
# 
containers:
  - name: myfrontend
    image: nginx
    volumeMounts:
    - mountPath: "/var/www/html"
      name: web
  volumes:
  - name: web
    persistentVolumeClaim:
      claimName: pvc-test
nimble sedge
#

First ensure tbe instances are available. Immediately after you provision the pod, check the logs. kubectl logs -n trident <pod name of controller> -c trident-main --tail=20 -f. Ensure storage class maps to right virtual pool.