Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 7 results
    • rsize and wsize not reflected in the mount option for NFS PersistentVolume
      https://kb.netapp.com/Cloud/Astra/Trident/rsize_and_wsize_not_reflected_in_the_mount_option_for_NFS_PersistentVolume
      Specified rsize or wsize in mountOptions of StorageClass or nfsMountOptions of Trident backend rsize and wsize specified in the configuration of StorageClass or Trident backend are not reflected in th...Specified rsize or wsize in mountOptions of StorageClass or nfsMountOptions of Trident backend rsize and wsize specified in the configuration of StorageClass or Trident backend are not reflected in the mount option for NFS PersistentVolume. [root@rhel3 setup]# tridentctl get backend BackendForNAS -o yaml -n trident | grep nfsMountOptions
    • How to place trident-operator pod on specific nodes
      https://kb.netapp.com/Cloud/Astra/Trident/How_to_place_trident-operator_pod_on_specific_nodes
      Applies to NetApp Astra Trident Deploying Trident operator manually Description The node where trident-operator pod is placed is undefined by default. This article describes the procedure for placing ...Applies to NetApp Astra Trident Deploying Trident operator manually Description The node where trident-operator pod is placed is undefined by default. This article describes the procedure for placing trident-operator pod on specific nodes in the case of deploying Trident operator manually.
    • Pod restart fails after worker node loses access to NFS PV
      https://kb.netapp.com/Cloud/Astra/Trident/Pod_restart_fails_after_worker_node_loses_access_to_NFS_PV
      NFS Persistent Volume (PV) Pod restart fails after worker node loses access to NFS PV Manually mounting the NFS PV on the worker node fails Warning FailedMount 40s kubelet MountVolume.SetUp failed for...NFS Persistent Volume (PV) Pod restart fails after worker node loses access to NFS PV Manually mounting the NFS PV on the worker node fails Warning FailedMount 40s kubelet MountVolume.SetUp failed for volume "<PVC>" : rpc error: code = DeadlineExceeded desc = context deadline exceeded Warning FailedMount 28s (x2 over 2m32s) kubelet Unable to attach or mount volumes: unmounted volumes=[<VOLUME>], unattached volumes=[], failed to process volumes=[]: timed out waiting for the condition
    • Trident mounts /dev/dm-N instead of /dev/mapper/mpathN
      https://kb.netapp.com/Cloud/Astra/Trident/Trident_mounts__dev_dm-N_instead_of__dev_mapper_mpathN
      Applies to NetApp Astra Trident Ubuntu ONTAP SAN driver iSCSI Multipathing Issue Volumes created via Trident have mount paths /dev/mapper/mpathN and /dev/dm-N coexisting Example: # df -h | grep /dev /...Applies to NetApp Astra Trident Ubuntu ONTAP SAN driver iSCSI Multipathing Issue Volumes created via Trident have mount paths /dev/mapper/mpathN and /dev/dm-N coexisting Example: # df -h | grep /dev /dev/mapper/mpathd 49G 76K 47G 1% /var/lib/kubelet/pods/[ID]/volumes/kubernetes.io~csi/pvc-[ID]/mount /dev/dm-1 30G 20G 8.7G 69% /var/lib/kubelet/pods/[ID]/volumes/kubernetes.io~csi/pvc-[ID]/mount /dev/dm-2 20G 4.2G 15G 23% /var/lib/kubelet/pods/[ID]/volumes/kubernetes.io~csi/pvc-[ID]/mount
    • PV is re-formatted when operating a rolling update for StatefulSet and moving nodes
      https://kb.netapp.com/Cloud/Astra/Trident/PV_is_re-formatted_when_operating_a_rolling_update_for_StatefulSet_and_moving_nodes
      Persistent Volume (PV) having a file system is reformatted when operating a rolling update for StatefulSet and moving nodes time="2020-07-19T03:25:40Z" level=debug msg="<<<< osutils.execCommandWithTim...Persistent Volume (PV) having a file system is reformatted when operating a rolling update for StatefulSet and moving nodes time="2020-07-19T03:25:40Z" level=debug msg="<<<< osutils.execCommandWithTimeout." time="2020-07-19T03:25:40Z" level=debug msg="Could not get FSType for device." time="2020-07-19T03:25:40Z" level=debug msg="Formatting LUN." time="2020-07-19T03:25:40Z" level=debug msg=">>>> osutils.formatVolume" device=/dev/dm-0 fsType=ext4
    • How does Trident handle CHAP Secrets when connecting to a SolidFire array
      https://kb.netapp.com/Cloud/Astra/Trident/How_does_Trident_handle_CHAP_Secrets_when_connecting_to_a_SolidFire_array
      When configuring CHAP for Trident to authenticate with a SolidFire array, the CHAP secrets come from the SolidFire Account. A Container which needs access to the volume doesn’t mount the SolidFire Vol...When configuring CHAP for Trident to authenticate with a SolidFire array, the CHAP secrets come from the SolidFire Account. A Container which needs access to the volume doesn’t mount the SolidFire Volume directly, the Host Client mounts the SolidFire Volume using standard iSCSI commands Trident gets the CHAP secrets from the SolidFire cluster by using Element API calls when a trident volume is created
    • Creating pod fails when worker node lacks IP for NFS communication
      https://kb.netapp.com/Cloud/Astra/Trident/Creating_pod_fails_when_worker_node_lacks_IP_for_NFS_communication
      Warning FailedMount 38s kubelet Unable to attach or mount volumes: unmounted volumes=[<VOLUME>], unattached volumes=[], failed to process volumes=[]: timed out waiting for the condition Warning Failed...Warning FailedMount 38s kubelet Unable to attach or mount volumes: unmounted volumes=[<VOLUME>], unattached volumes=[], failed to process volumes=[]: timed out waiting for the condition Warning FailedMount 32s kubelet MountVolume.SetUp failed for volume "<PVC>" : rpc error: code = Internal desc = error mounting NFS volume <IP>:/<NFS> on mountpoint /var/lib/kubelet/pods/<ID>/volumes/kubernetes.io~csi/<PVC>/mount: exit status 32