Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 13 results
    • After ETCD database was restored in OpenShift, the Trident pods are not properly working
      https://kb.netapp.com/Cloud/Astra/Trident/After_ETCD_database_was_restored_in_OpenShift_the_Trident_pods_are_not_properly_working
      Applies to RedHat OpenShift 4.8 NetApp Astra Trident NetApp Ontap 9.X Issue After ETCD database was restored in OpenShift cluster, the Trident pods do not properly connect and are not working as expec...Applies to RedHat OpenShift 4.8 NetApp Astra Trident NetApp Ontap 9.X Issue After ETCD database was restored in OpenShift cluster, the Trident pods do not properly connect and are not working as expected
    • PVC mount with LUKS encryption enabled fails with "LUKS passphrase cannot be empty"
      https://kb.netapp.com/Cloud/Astra/Trident/PVC_mount_with_LUKS_encryption_enabled_fails_with_LUKS_passphrase_cannot_be_empty
      After enabling LUKS encryption for volumes on Trident, mounting a non-LUKS encrypted PVC using OpenShift fails with the following error: Warning FailedMount pod/<PV_Id> MountVolume.MountDevice failed ...After enabling LUKS encryption for volumes on Trident, mounting a non-LUKS encrypted PVC using OpenShift fails with the following error: Warning FailedMount pod/<PV_Id> MountVolume.MountDevice failed for volume "<PVC_Id>" : rpc error: code = Internal desc = rpc error: code = Internal desc = failed to stage volume: LUKS passphrase cannot be empty
    • trident-operator fails to start with "/trident-operator: no such file or directory"
      https://kb.netapp.com/Cloud/Astra/Trident/trident_operator_fails_to_start_with_trident_operator__no_such_file_or_directory
      Warning Failed 2m3s (x3 over 2m31s) kubelet (combined from similar events): Error: container create failed: time="2024-05-14T09:32:22Z" level=error msg="runc create failed: unable to start container p...Warning Failed 2m3s (x3 over 2m31s) kubelet (combined from similar events): Error: container create failed: time="2024-05-14T09:32:22Z" level=error msg="runc create failed: unable to start container process: exec: \"/trident-operator\": stat /trident-operator: no such file or directory"
    • Trident PV doesn't move to a new OpenShift node in the cluster when one OpenShift node fails
      https://kb.netapp.com/Cloud/Astra/Trident/Trident_PV_doesn_t_move_to_a_new_OpenShift_node_in_the_cluster_when_one_OpenShift_node_fails
      Applies to RedHat OpenShift Container Platform 4.9 NetApp Astra Trident 22.01.1 NetApp ontap 9.X Issue When a PV is attached to a pod running in an OpenShift node and that node fails, the PV should ge...Applies to RedHat OpenShift Container Platform 4.9 NetApp Astra Trident 22.01.1 NetApp ontap 9.X Issue When a PV is attached to a pod running in an OpenShift node and that node fails, the PV should get attached to a different pod scheduled in another OpenShift node in the same cluster
    • Trident does not properly initialize after worker nodes were restarted
      https://kb.netapp.com/Cloud/Astra/Trident/Trident_does_not_properly_initialize_after_worker_nodes_were_restarted
      Applies to RedHat OpenShift Container Platform (OCP) 4.X NetApp Trident CSI plugin 23.X NetApp ONTAP 9.X Issue After restarting the worker nodes in the OCP cluster, Trident does not properly initializ...Applies to RedHat OpenShift Container Platform (OCP) 4.X NetApp Trident CSI plugin 23.X NetApp ONTAP 9.X Issue After restarting the worker nodes in the OCP cluster, Trident does not properly initialize and existing PVCs can't be mounted
    • 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.
    • NetApp Astra Trident backend fails to be created
      https://kb.netapp.com/Cloud/Astra/Trident/NetApp_Astra_Trident_backend_fails_to_be_created
      NetApp Astra Trident 22.10 Red Hat OpenShift management network is different than the storage network When creating a Trident backend, it fails with the following error: time="YYYY-MM-DDThh:mm:ssZ" le...NetApp Astra Trident 22.10 Red Hat OpenShift management network is different than the storage network When creating a Trident backend, it fails with the following error: time="YYYY-MM-DDThh:mm:ssZ" level=error msg="Could not initialize storage driver." ontap-nas driver: could not create Data ONTAP API client: error creating ONTAP API client: error reading SVM details: Post time="YYYY-MM-DDThh:mm:ssZ" level=debug msg="Failed storage backend."
    • 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
    • TridentbackendConfig (tbe) gets stuck and new PVCs for this backend, can't be mounted anymore
      https://kb.netapp.com/Cloud/Astra/Trident/TridentbackendConfig_tbe_gets_stuck_and_new_PVCs_for_this_backend_can_t_be_mounted_anymore
      Applies to NetApp Astra Trident NFS protocol Issue When creating new PVCs for a Trident backend, the volume mount fails with the error below: MountVolume.SetUp failed for volume "pvc-xxxxxxxx-yyyy-zzz...Applies to NetApp Astra Trident NFS protocol Issue When creating new PVCs for a Trident backend, the volume mount fails with the error below: MountVolume.SetUp failed for volume "pvc-xxxxxxxx-yyyy-zzzz-xxxx-yyyyyyyyyyyy" : rpc error: code = DeadlineExceeded desc = context deadline exceeded Warning FailedMount 24s kubelet Unable to attach or mount volumes: unmounted
    • Trident pods get stuck in ContainerCreating status, after upgrading the OpenShift version
      https://kb.netapp.com/Cloud/Astra/Trident/Trident_pods_get_stuck_in_ContainerCreating_status_after_upgrading_the_OpenShift_version
      Applies to RedHat OpenShift Container Platform (OCP) 4.15,4.16 NetApp AstraTrident 24.X OCP with OVS Networking Issue After upgrading OCP to version 4.15 or 4.16, the Trident pods gets stuck in Contai...Applies to RedHat OpenShift Container Platform (OCP) 4.15,4.16 NetApp AstraTrident 24.X OCP with OVS Networking Issue After upgrading OCP to version 4.15 or 4.16, the Trident pods gets stuck in ContainerCreating status
    • Access denied to root directory in a container running in RedHat OpenShift platform
      https://kb.netapp.com/Cloud/Astra/Trident/Access_denied_to_root_directory_in_a_container_running_in_RedHat_OpenShift_platform
      Applies to Redhat OpenShift Container Platform (OCP) 4.x NFS v3 protocol NetApp ontap 9.X LDAP integration with OpenShift and ontap Issue Created a deployment in the OpenShift platform The deployment ...Applies to Redhat OpenShift Container Platform (OCP) 4.x NFS v3 protocol NetApp ontap 9.X LDAP integration with OpenShift and ontap Issue Created a deployment in the OpenShift platform The deployment uses a Trident PersistentVolume (PV) from an ontap nfs volume When connecting to the container in a shell, access to the mount path is not allowed (permission denied)