NetApp Trident
NetApp Trident
Other Resources
- Trident Backend Creation Fails in OpenShift with “Failed to apply the backend update; problem initializing storage driver ‘ontap-san’”Sep, 2026
- TRID-20579: Missing CHAP credentials on second portal after node/ONTAP upgradeSep, 2026
- Can export policy alone protect Trident-created ONTAP NFS volume across OCP clusters?Sep, 2026
- TRID-20466: Trident 26.02 generates warning that Kubernetes 1.36 is not supportedSep, 2026
- PVC bound but volume not found in Trident after migration, 404NotFound ErrorSep, 2026
- Can storageDriverName be changed after creating a Backend from TBC?Sep, 2026
- Trident Leaves Orphaned iSCSI Multipath Devices and Stale Mounts After Pod DetachSep, 2026
- TRID-20246: [DOC BUG]Trident Storage configuration options page contentsSep, 2026
- TRID-20202: ontap-nas export policy rules deleted on TridentBackendConfig update races with backend bootstrapSep, 2026
- Trident NVMe PVC clone failures after upgrade to 26.02/26.06Sep, 2026
- Trident NFS export rules deleted after controller restartSep, 2026
- Netapp Trident Installation failure in OpenShift due to incomplete image mirroringSep, 2026
- Trident IssuesSep, 2026
- Does Trident support VolumeAttributesClass?Sep, 2026
- Trident not preserving existing annotations after update from v26.02.0 to v26.02.1Aug, 2026
- Pods experience latency during startup in OpenShift clusterAug, 2026
- Astra Trident LUN info retrieval errors on ONTAP FlexClone volumesAug, 2026
- TridentProtect backup fails with specified key does not existAug, 2026
- Trident Protect backup fails with "insufficient storage available in the Vserver"Aug, 2026
- NetApp CSI Integration Fails After OpenShift Node Restart – PVCs Stuck, VolumeAttachment Terminating, Trident Components MissingAug, 2026
- Trident Backend Creation Fails in OpenShift with “Failed to apply the backend update; problem initializing storage driver ‘ontap-san’”Sep, 2026
- Kubernetes PVC provisioning fails via Trident after ONTAP upgrade due to transient API communication issueSep, 2026
- TRID-20579: Missing CHAP credentials on second portal after node/ONTAP upgradeSep, 2026
- TRID-20246: [DOC BUG]Trident Storage configuration options page contentsSep, 2026
- TRID-20202: ontap-nas export policy rules deleted on TridentBackendConfig update races with backend bootstrapSep, 2026
- Trident Leaves Orphaned iSCSI Multipath Devices and Stale Mounts After Pod DetachSep, 2026
- Can export policy alone protect Trident-created ONTAP NFS volume across OCP clusters?Sep, 2026
- Trident slow Volume Attachment after Data Center FailoverSep, 2026
- FSX Trident Backend Not Created Automatically via StorageClassSep, 2026
- TRID-20466: Trident 26.02 generates warning that Kubernetes 1.36 is not supportedSep, 2026
- PVC bound but volume not found in Trident after migration, 404NotFound ErrorSep, 2026
- Trident Protect SnapMirror Relationship Remains Uninitialized Due to Incorrect SVM Peering ConfigurationSep, 2026
- Trident fails to create PVC with error: could not find aggregateSep, 2026
- Can storageDriverName be changed after creating a Backend from TBC?Sep, 2026
- Trident NVMe PVC clone failures after upgrade to 26.02/26.06Sep, 2026
- TridentProtect backup fails with specified key does not existSep, 2026
- Pods experience latency during startup in OpenShift clusterSep, 2026
- Trident NFS export rules deleted after controller restartSep, 2026
- Netapp Trident Installation failure in OpenShift due to incomplete image mirroringSep, 2026
- Trident IssuesSep, 2026
- Trident Issues
- TRID-20202: ontap-nas export policy rules deleted on TridentBackendConfig update races with backend bootstrap
- TRID-20246: [DOC BUG]Trident Storage configuration options page contents
- TRID-20466: Trident 26.02 generates warning that Kubernetes 1.36 is not supported
- TRID-20579: Missing CHAP credentials on second portal after node/ONTAP upgrade
- Trident KBs
- Access denied to root directory in a container running in RedHat OpenShift platform
- After creating a Pod and PVC, the Pod does not start with MountVolume.SetUp failed error
- After increase work node trident pod crash with Reason: CrashLoopBackOff
- After migrating to a new ontap cluster, existing PVCs or new PVCs are not properly working
- After OCP upgrade daemonset pods stuck at container creating state
- After OpenShift and Trident upgrade, some PVs can't be properly accessed from pods
- After reinstalling Trident, volume provisioning fails with "unknown storage class" error
- After restarting the Trident controller, the Trident nodes take a long time to re-register with the controller
- After the EOA of Astra Control Center, is it necessary to configure Trident-ACP when setting up a new Trident deployment?
- After Trident upgrade to 25.06 release, storage classes are not properly detected by Trident
- After upgrading Trident to 24.10, empty export policies are created with non existing rules
- After worker node reboot, Trident backend is not showing up anymore
- AMR SnapMirror schedule not working
- Application files within Trident volumes get: Permission Denied error
- Application pods fail to mount using Trident due to IBM queue manager
- Application pods fail to schedule on new node after an abrupt node shutdown/reboot
- Application pods mount fails - orphaned pods reported in kubelet log
- Application pod fail to run with error: failed to stage volume: no new session to establish and existing session(s) might be in unhealthy state
- AppMirrorRelationship (AMR) Stuck Waiting for Destination PVCs to be Bound
- AppMirrorUpdate objects accumulate on destination cluster in Trident Protect
- Appmirror not replicating
- Are Trident 25.10 Deployments Affected by CVE-2023-45288 and CVE-2025-22872?
- Are wildcard characters (*) allowed in Trident spec.storagePrefix values
- Astra Trident fails to provision a PVC with the error "no available topology found"
- Astra Trident install/upgrade - failed to create the Trident pod security policy
- Astra Trident LUN info retrieval errors on ONTAP FlexClone volumes
- Astra Trident: mount volume failed with error "Could not find iSCSI device"
- Astra Trident TridentBackendConfig goes to lost state after changing UID
- Astra Trident: unable to mount the volume with error "unable to attach or mount volumes: timed out waiting for the condition"
- Astra Trident volume provisioning fails with Aggregate not found error
- Astra Trident: Trident Backend Configuration Error Due to Incorrect or Missing Credentials
- Attach PV on NVMe/TCP backend fails by REST API /protocols/nvme/subsystem-maps error
- autoexports does not update export policies for snapshot PVCs - mount exit status 32
- Automatic Volume Expansion Not Working After Upgrade to Trident 26.02
- Backups of PVCs using Commvault application failed
- Backup of very large PVCs using Trident Protect times out
- Cannot mount a PVC based on a snapshot of an XFS filesystem PVC on the same OpenShift node
- Can Astra Trident delete FSx managed backups?
- Can export policy alone protect Trident-created ONTAP NFS volume across OCP clusters?
- Can Helm add annotations to the Trident controller or node pods?
- Can multiple aggregates be defined in a Trident backend? tbc?
- Can new VLANs be added to the Trident configuration and old VLANs removed
- Can Open Shift be integrated with Astra Trident?
- Can storageDriverName be changed after creating a Backend from TBC?
- Can SVM custom roles be copied to another SVM
- Can Trident be configured to use only the NFSv3 vs. NFSv4 protocol?
- Can Trident be switched from a tridentctl installation to a Helm installation?
- Can Trident be used to manage ONTAP deduplication/compression settings?
- Can Trident dynamically create and attach volumes using a CSI driver?
- Can Trident POD be re-created without impact for already provisioned PVs?
- Can Trident reassign volume ownership on node move?
- Can Trident set the schedule for a SnapMirror relationship it has configured?
- Can Trident use Multus on OpenShift for the storage network?
- Can Trident use ONTAP S3 Buckets as a Storage Backend in Kubernetes?
- Can Trident volumes be moved between aggregates in storage cluster non-disruptively?
- Can Trident with Kubernetes or Openshift reduce the size of a deployed, persistent volume (PV) ?
- Can we run trident node pods only on Worker node and not run in Controller node?
- cli trindent-protect doesn't work in a Rancher environment
- Clone of a PVC fails when using Velero backup Solution
- Clone split does not complete in Trident
- Cohesity Backup Fails Due to Trident Snapshot Deletion Issues in Kubernetes Environments
- Commvault backups of Kubernetes clusters fail after running for long time due to a timeout
- Configuration Mismatch Between Trident and Openshift after Ransomware policy change
- Configure an Astra Trident backend using an Active Directory account
- Connection Timeout Issue on Trident NFS LIF due to no response to port 2049
- Connection Timeout Issue on Trident NFS LIF due to no response to port 443
- Containerized applications having issues in a kubernetes cluster
- Containers lose access to NVME namespace in a Trident environment
- Cosmetic error seen after Trident upgrade to 25.02.1
- Could not find backend for PVC or during update after a Trident upgrade
- "Could not find iSCSI device: no devices present yet" is shown before "Adding iSCSI session info"
- CPU and memory requests and limits are not created by default for Trident pods
- Create san pod fail with error failed to stage volume: no devices present yet
- Creating a PVC from a Trident PVC Snapshot cannot be created in an alternate backend
- CSI-Snapshot creation via trident fails due to "too many snapshots on volume"
- CSI error after volume migration: Error processing "csi-id": failed to detach: persistentvolume "pvc" not found
- Customized timeout setting for Trident, as the default timeout is 30 seconds, which can be not large enough
- CVE-2024-24790 security vulnerability reported in Trident 24.06
- DB2 Restore Failure with Trident Protect: “No Space Left on Device” Error
- Delay in creating multiple PVCs at the same time and mounting them in pods
- Deleted Data from PVC Not Reclaimed on ONTAP Storage with Trident CSI
- Deploying multiple Trident LUN PVs can cause multiconfd to hang
- Deploy Astra Trident in a RedHat OpenShift cluster using the sha digest
- Docker trident-plugin will not start after upgrade
- Does Astra Trident support Kasten snapshots on NetApp storage?
- Does Astra Trident support zero-downtime upgrades?
- Does communication failure between the kubelet and the Trident CSI plugin causes unexpected node reboot?
- Does enabling Kerberos in-flight encryption in Trident and ONTAP prevent unauthorized NFS access from non-privileged pods in OpenShift
- Does missing node IP addresses from automatic export policies issue fixed in 24.10.1?
- Does NetApp provide a CSI driver for OpenShift?
- Does NetApp provide official Docker images for offline installs?
- Does the aggregate that provides storage for Trident have to be a new aggregate?
- Does the behavior of limitAggregateUsage in the Trident backend configuration depending on other settings, like aggregate, or provisioning is thin or thick?
- Does the NetApp Trident ontap-san driver create multiple LUNs inside a single FlexVol volume?
- Does the root_user access images in Trident ver 25.10.x?
- Does tridentctl update to change SVM name for backend have any impact on IO?
- Does Trident affect Pod I/O performance after a PV is mounted?
- Does Trident attempt to detach volume provisioned by one backend using another?
- Does Trident create an export policy with root squashing when autoExportPolicy is enabled?
- Does Trident have an option to mount PVs with NFSv4.1 enabled and NFSv4.2 disabled?
- Does Trident impose a limit on the number of PVs that can be created with the ontap-nas driver?
- Does Trident impose a maximum size limit on PVs?
- Does Trident provision ONTAP volumes while creating PV without requesting PVC?
- Does Trident require a license to install and operate?
- Does Trident support configuring inodes on volume creation and expansion?
- Does Trident support ONTAP Tamperproof snapshots?
- Does Trident Support SnapLock?
- Does Trident support VolumeAttributesClass?
- Does Trident support volume snapshots of NetApp ONTAP NAS Economy volumes?
- Does Trident works with settings Non-Graceful Node Shutdown (NGNS) without configuring on Kubernetes
- Do file and block storage CSIs in OpenShift require separate Trident installations?
- Do tridentnoderemediations and tridentnoderemediationtemplates work when enableForceDetach is disabled?
- Do Trident backends with different storagePrefix create qtrees in different volumes?
- Do Trident for Docker's Get-Volume requests influence NDMP restorability from AQUIM ?
- During backup of Trident volumes, alerts are raised in the ontap cluster related to "Not enough disk space for the operation"
- During trident-csi pod up generate message A multipath device may not exist
- Enable Certificate-based Authentication for a Trident backend
- Enforcing Kubernetes limitVolumeSize Policy with Trident: Aggregate Visibility Limitations for SVM-Scoped Roles in ONTAP
- Error "400 Bad Request" when creating a Trident backend
- Error initializing ontap-nas driver when creating a Trident backend
- Error nblade.execsOverLimit in ontap cluster, accessed by a Kubernetes cluster
- Error Permission Denied when Mounting PV created by trident to host
- Error "SSL_ERROR_SYSCALL in connection to" when setting up Astra Trident for ontap
- Error when Pods are rescheduled - error publishing ontap-san driver: problem mapping LUN. attr: LUN already mapped to initiator(s) in this group
- Error when unmounting file "Failed to open volume data file vol_data.json"
- Error when upgrading Trident err: unsupported Trident image version
- Even if svm is not specified in the backend config, the backend contains svm, is this expected?
- Excessive Trident autogrow events after VMware to OpenShift migration
- Existing Trident backend requires migration to a new backend
- Export-policy rules are not properly created by Trident when using autoExportPolicy in a Trident backend
- Export policy wiped on backend update
- Extract or download files from a Trident PVC attached to a kubernetes pod
- Extra space is wasted when formatting a PVC in Trident
- FailedMapVolume in Trident: Context Deadline Exceeded
- Failed dm-devices visible after Upgrade of Trident from pre-22.07 to 22.10 or later
- Failed to add backend on Trident with Error "API status: failed, Reason: Specified vserver not found, Code: 15698"
- Failed to add Backend on Trident with Error "specified vserver not found, Code: 15698"
- Failed to create a pvc with error no available storage for access mode
- Failed to create volume using Trident with Error "Maximum number of volumes reached on node"
- Failed to provision a Trident volume because aggregate is in unknown state
- Failed to provision new volumes using trident after number of volumes on SVM reached to maximum limit
- Failed to provision volume with StorageClass "<sc>" : rpc error: code = unknown storage class: <sc>
- Failed to pull image "docker.io/netapp/trident-autosupport"
- Failed to spin up a pod with error relabel failed
- Failure to add Trident backend definition error 401: incorrect or missing credentials
- Failure to duplicate export policy causes failed mount on new nodes
- Failure to expand a Trident PVC
- Fail to use certificate authentication against data vserver
- Files created inside Trident PV have owner and group 'nobody'
- Formatting of a Trident NVME device fails when using LUKS encryption
- Frequent “RecurrenceRuleCompliant=false” Conditions on AppMirror Relationships
- FSX Trident Backend Not Created Automatically via StorageClass
- Getting Error invalid character 'W' when running tridentctl commands in 24.02
- Helm upgrade error after Kubernetes Upgrade to 1.25 with Trident installed
- High memory consumption by Trident csi-resizer container
- High Worker Node CPU Usage Caused by Trident Orphaned Volumes Referencing Deleted Backend
- How best to collect Trident logs in a Kubernetes or Openshift environment
- How can the value for SplitOnClone be set in Trident?
- How can Trident reuse an existing backend volume
- How can retention be enforced in AWS s3 buckets with Trident Protect?
- How does Astra Trident work with ONTAP FlexGroup volumes?
- How does Trident behave when creating clones with splitOnClone set to true?
- How does Trident handle a dataLIF setting for ontap-san driver with multipathing
- How does Trident handle CHAP Secrets when connecting to a SolidFire array
- How does Trident inherit the Kubernetes namespace labels to the comments that is added about the volume usage ?
- How does Trident select an aggregate when creating a Persistent Volume (PV)?
- How do we confirm if policy "adaptiveQosPolicy" has been applied on SAN volumes ?
- How is round robin configured in a Trident backend
- How is the skip recovery queue for ONTAP volume applied when Trident deletes PVC?
- How to add Grafana dashboard to monitor Trident Kubernetes
- How to attach the same Trident created PVC to multiple k8s clusters
- How to Avoid Downtime When Migrating Trident SVM/LIFs to a New ONTAP Controller
- How to change a Kubernetes secret configuration
- How to Change NFS Export Policy for Trident-Managed Volumes in OpenShift Without Disrupting Existing Setup
- How to Cleanly Uninstall Trident Installed with Helm for OpenShift environment
- How to configure a snapshot reserve for a persistent volume (PV) provisioned by Trident ?
- How to configure no_root_squash export policy for Trident PersistentVolume(PV)
- How to create an RFE for Trident
- How to create an RWX NAS PV with setuid bit for group using Trident backend
- How to Create a LUN with XFS Filesystem in Kubernetes using NetApp Trident and iSCSI ?
- How to disable Trident iscsi self healing feature
- How to enable backend debug logging in Trident
- How to Enable Persistent Storage for IBM Power Linux PPC64LE Architecture with Trident
- How to Enable Snapshots for a Single Trident-Managed Application in an OpenShift Cluster
- How to enable Trident debug and debugTraceFlag for more verbose logging
- How to ensure clones split on creation in Trident
- How to fix file system errors with Trident or Kubernetes SAN PVs
- How to import an ONTAP volume into a trident backend stuck in a loop
- How to import an ONTAP volume into a Trident backend using same Pod
- How to modify autosupportProxy after tridentctl install
- How to move Trident PVs from one Backend to another
- How to optimize NFS mounts for Trident on OpenShift
- How to Override NetApp Trident and CSI Container Registries Using Helm
- How to prepare the worker nodes for Astra Trident
- How to prevent Trident to hit 1000 volumes in an Aggregate
- How to pull the images and place it private repository
- How to recover trident PVCs after having deleted the trident CRD information
- How to recreate a deleted tbe when the tbc still exists
- How to remove a Storage Class from Trident Backend
- How to setup a limited ONTAP role for Astra Trident
- How to setup fsGroup usage with Trident ONTAP drivers
- How to setup regular CSI snapshots on Trident provided PV ONTAP volumes
- How to set hostNetwork to true on trident-controller
- How to set or update resource requests/limits for Trident components For example - controller or node pods?
- How to specify backends or aggregates using regex in a Storage Class
- How to test connectivity to Trident CSI Controller from a particular Kubernetes node
- How to test ONTAP API calls from a Linux host
- How to Uninstall Trident and WIPEOUT All CRD’s
- How to uninstall Trident without removing CRD's
- How to update a SolidFire Backend to use a new Tenant account
- How to update snapshot reserve on existing Trident volumes
- How to update the trident backend user-state
- How to upgrade Trident when csi and trident images are in private repository
- How to Verify If ONTAPI (ZAPI) Calls Are Still Being Processed in ONTAP with Trident
- How Trident uses labels to select the correct backend
- If there are multiple backends, how does Trident select which backend to use?
- Immutable Linux OS for use with Trident
- Increasing inode for container is reflected for NAS but is not reflected for SAN
- input output error on the mount point of an ontap-san XFS formatted Trident PV
- "Invalid argument" error seen in pods after an ONTAP upgrade
- In Trident, is it possible to configure multiple addresses (including both IPv4 and IPv6) as management LIFs or data LIFs for a single Backend?
- iscsi errors in host logs
- iSCSI PVC creation fails with "failed to stage volume: iSCSI login failed"
- iSCSI timeouts in Trident environment prolonging pod provisioning in OpenShift
- Is CSIStorageCapacity validated from the perspective of Trident?
- Is it feasible to restrict the permissions of Trident containers.?
- Is it possible to change any snapshot or volume label from Trident
- Is it possible to change the NFS protocol version on an existing mount ?
- Is it possible to create a VM from a template on one backend and have the resulting VM created on a different backend in a NetApp ONTAP environment using Trident?
- Is it possible to determine from Trident logs which kubectl user or ServiceAccount created a PVC or PV?
- Is it possible to modify Storage Class to add excludeStoragePools after PV creation?
- Is it possible to set a volume creation limit in Trident?
- Is it possible to set priorityClassName for Trident pods when installing via Helm?
- Is it possible to switch from Trident Helm Operator install to Operator.Hub
- Is it possible to update the DataLIF on the trident backend?
- Is it possible to update the Management LIF on the trident backend?
- Is manual SCC assignment (oc adm policy add-scc-to-user) required when installing Trident on OpenShift?
- Is Mirroring of FlexGroups supported in Trident Protect and Trident?
- Is "node.session.scan = manual" in iscsid.conf required for Trident?
- Is ONTAP volume automatically resized by Trident when resizing PVC using ONTAP backend?
- Is StorageGRID supported as a backend storage for NetApp Trident?
- Is that possible to set Volume tags via Trident
- Is there any way to validate concurrency is working in Trident?
- Is there an official location for csi-proxy.exe?
- Is there a possibility that NetApp Trident is removed from the OpenShift OperatorHub, and if so, is this documented?
- Is there a setting to enable advanced capacity balancing when creating a FlexGroup from Trident?
- Is there a way to specify the path to kubectl in tridentctl when kubectl is not in the $PATH?
- Is tridentctl needed in a Trident environment that was installed without using tridentctl?
- Is Trident affected by ONTAP upgrades?
- K8S - waiting for a volume to be created, either by external provisioner
- kubelet error message "scheme "" not registered, fallback to default scheme"
- KubePodNotReady Alerts and context deadline exceeded Errors in OpenShift ADP Backup Pods with NetApp Trident
- Kubernetes create PVC with error "no available backends for storage class media sas"
- Kubernetes - mount: wrong fs type, bad option, bad superblock
- Kubernetes NFS PVC Mount Fails with “access denied by server” – ONTAP SVM Root Volume Export Policy Missing Client Rule
- Kubernetes / OpenShift volume mount fails with permission denied error
- Kubernetes Pods Fail to Mount iSCSI Volumes: “rpc error: code=Internal desc=failed to stage volume: iSCSI login failed” Due to CHAP Secret Mismatch
- Kubernetes Pods Stuck in Terminating/BackOff State When NetApp Storage Is Unavailable
- Kubernetes PVCs Go Read-Only Due to Multipath Device Serial Mismatch and Stale Device Maps
- Kubernetes PVC provisioning fails via Trident after ONTAP upgrade due to transient API communication issue
- Kubernetes Snapshot Creation Fails with “rpc error: code = DeadlineExceeded desc = context deadline exceeded” for NetApp ONTAP PVCs via Trident
- Kubernetes Trident TMR Configuration Fails: “No available backends for storage class” and Replication Not Detected
- Kubernetes unable to connect over port 2049 with error "connection refused".
- Kubernetes VM fails to attach volume when PersistentVolume is stuck in deletion state with reclaimPolicy set to Delete
- Kubernetes worker node's initiator not logging properly into NetApp ontap targets
- Large Number of Volume Clones Left Behind After Cohesity Backup in Kubernetes/Trident Environments
- LUN assignments appear to change on Trident-provisioned volumes
- LUN Assignment Change Notifications During Trident PVC Provisioning in Kubernetes/OpenShift Environments
- Management connection to SVM restored, but Trident backend shows offline
- Minimizing exec RBAC Permissions for NetApp Trident Operator in Kubernetes
- Modifying snapshotReserve of backend is not reflected to existing Trident PV
- Mount fails after OpenShift upgrade: failed to create newCsiDriverClient: driver name csi.trident.netapp.io not found in the list of registered CSI drivers
- nas-economy driver creates extra qtree pool volumes
- NetApp Astra Trident backend fails to be created
- NetApp CSI Integration Fails After OpenShift Node Restart – PVCs Stuck, VolumeAttachment Terminating, Trident Components Missing
- NetApp Trident, Red Hat OpenShift CSI and private registry FAQs
- NetApp Trident errors after deletion of node
- Netapp Trident Installation failure in OpenShift due to incomplete image mirroring
- NetApp Trident Unable to create PV after SVM migration
- Network issue causes Trident backend offline
- Newly created PVC is in a Pending state
- New PVCs are provisioned as thick instead of thin
- New PVCs created with NFS plugin nfs-subdir-external-provisioner get stuck in Pending status
- New Trident economy PVCs can't be properly provisioned
- Trident fails to create PVC with error: could not find aggregate
- New Trident releases are not seen in the OCP Software Catalog
- New VMs created in OpenShift overload the trident controller
- New volume size not seen in RedHat OpenShift cluster and Trident
- NFSv4.2 “Permission Denied” When Using ONTAP-NAS-Economy Driver with Trident
- NFS export policy is missing one or more Kubernetes node's IP address
- NFS PVC mount fails on ONTAP with Trident in Kubernetes with Init 0
- Node down causes NFS PVC unresponsive if LIF does not fail over to another node
- Node prep crashes in OCP 4.19 Trident Node pods go into crash loop backoff
- Node registration to Trident CSI controller fails by communication error
- No available backends for storage class SC-NAME
- Object and image issues from failovers and failback operations on a trident protect installation in an Openshift cluster
- OC-Mirror error when using the latest version of the Trident Operator v25.10
- ONTAP-SAN Economy Driver fails to provision LUNs when there is a dash in the storagePrefix
- ontap-san type backend can show XFS errors when using that filesystem on RHEL7.3
- ONTAP Local User Account Lockout When Shared Between Trident and System Manager
- ONTAP role for Astra Trident fails to find larger PVs for operations
- ONTAP Snapshots Accumulate and Block PVC Clone Operations with Trident (Cannot Exceed Maximum Number of Snapshot Copies)
- ONTAP Trident volumes are no longer recognized for operations after MCC/DR switchover
- ONTAP Volumes Not Deleted After PVC Deletion in OpenShift
- On some worker nodes, OpenShift VIRT VMs get stuck in provisioning status with Trident SAN volumes
- OpenShift error: "Unable to mount or attach CIFS volumes: unmounted"
- OpenShift Pods Fail to Mount NFS Volumes via Trident CSI: Intermittent “mount: exit status 32”
- OpenShift Pods Fail to Start After SVM DR Failover/Failback with NetApp Trident — “backend BackendForNFS is not Online or Deleting”
- OpenShift produces CDIStorageProfileIncomplete error when using selector labels
- OpenShift/Trident: Unable to Create RWX PVCs with ONTAP-SAN Backend
- Openshift upgrade may cause trident-controller to not start anymore
- OpenShift Virtualization VM in paused status with error: low-level IO error detected
- OpenShift VM does not properly boot, once scheduled to a worker node
- Performance Regression with NetApp iSCSI LUNs on Ubuntu 24.04 and 26.04
- Permissions issue when creating a PVC in OpenShift
- Permission denied by user account inside POD on Trident ontap-san(-economy) PV
- Persistent Volumes Not Detaching During Node Rotation
- Persistent Volume Claim (PVC) Creation Fails for Both ISCSI and NFS Backends in Trident/Astra on OpenShift
- Pods accessing Trident provided NFS PVs fail with Permission Denied on certain nodes
- PODs come online again very slowly during Kubernetes node upgrades
- Pods experience latency during startup in OpenShift cluster
- Pods Stuck in Terminating State or Multi-Attach Error During DR Activity with NetApp Trident CSI on OpenShift
- Pods stuck in terminating state w/error: Failed to statfs due to timeout
- Pods Unable to Spin Up Due to “Failed Attach Volume” Error in OpenShift with NetApp Trident
- Pod can't mount a 17 TBytes PVC
- Pod can't attach a volume and getting a multiattach error
- POD creation fails with error publishing ontap-san driver: no matching WWPN found for node 'wwnn of svm FC lif'
- Pod failing to attach Persistent Volume Claim (PVC)
- Pod fails to mount PVC using NFS when UserNamespacesSupport is enabled on Kubernetes
- Pod is unable to attach and mount the Persistent Volume (PV) because it is marked for deletion
- Pod is unable to mount PVC when IPsec tunnel is established
- Pod Mount Failure After Upgrading Trident to 25.06.0
- Pod restart fails after worker node loses access to NFS PV
- Pod state error with "multipath device not found when it is expected"
- Pod Stuck with PVC Attach Error failed to stage volume: multipath device not found when it is expected
- POD with Trident SAN or NAS RWO PV goes offline when moving to another node
- "Portal is missing LUN Number(s)" warning is output repeatedly
- Process to promote secondary PVC during a planned failover with Trident
- Promoting a tridentSnapMirror caused Vserver temporarily locked from changes
- PVCs are hanging in termination due to the PV's ONTAP volume not being deleted
- PVCs can't be properly mounted in worker nodes
- PVCs can't be properly mounted and getting error "exit status 32"
- PVCs do not mount to a pod due to multiple controllers
- PVC and related PV creation and bound take several minutes to complete
- PVC Attach Failure with “LUN already mapped to initiator(s) in this group” After Pod Migration in Kubernetes with Trident and ONTAP SAN
- PVC bound but volume not found in Trident after migration, 404NotFound Error
- PVC creation fails when using encryption in the Trident backend definition
- PVC creation fails with the error Aggregate not found Reason: entry doesn't exist
- PVC Expansion Fails with “failed to expand pvc with Expander.NodeExpand failed to expand the volume: rpc error: desc=exit status 1” in OpenShift/Trident/ONTAP
- PVC mount fails with error "no available storage for access mode: ReadWriteOnce"
- PVC mount fails with error: MountVolume.MountDevice failed for volume "pvc-ID" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
- PVC mount with LUKS encryption enabled fails with "LUKS passphrase cannot be empty"
- PVC Provisioning Fails in OpenShift with Trident: “could not find aggregate, cannot check aggregate provisioning limits” After Aggregate Removal
- PVC Provisioning Failure Over FC with NetApp Trident: Initiators Missing from FC igroup
- PVC Resize and Provisioning Operations Hang After Upgrade to Trident 26.02
- PVC resize attempt in Petabytes caused resize operation stuck and cannot be cancelled
- PVC Resize Concurrent with Pod Termination Causes Multipath Device Mismatch and CSI Unmount Failure
- PV is stuck in terminating state failing to delete
- PV not mounted to pod when creating multiple PVCs at the same time with SVM using LSM
- qcow2 image upload fails with permission denied using ontap-san in OpenShift
- Random backups of Trident PVCs fail with PowerProtect Data Manager
- Resize of PVC leaves it in a faulted state
- Resource limits not set in Trident pods
- Restart of POD fails with error iSCSI login failed after adding new iSCSI LIFs and removing old iSCSI LIFs in ONTAP
- Restore Trident backend.json configuration created by tridentctl
- Restoring Trident Protect CRDs and AMRs after upgrade and cleanup job
- RKE2 Trident upgrade failed with error: Failed to install Trident; err: failed to create or patch Trident daemonset trident-node-linux
- rsize and wsize not reflected in the mount option for NFS PersistentVolume
- S3 driver for Astra Trident
- Shared PVC across Namespaces are stuck in Pending
- Simulate trident install with helm fails with "ensure CRDs are installed first"
- Since upgrading Trident to 25.06.1 getting errors with provisioning /de-provisioning of NFS exports
- SnapCenter Oracle backup retention is failing on existing clone references
- SnapMirror Policy "MirrorLatest" Not Honored in Trident TMR – Policy and Schedule Mismatch
- Snapshot creation fails with error 'Could not create snapshot, acp is not enabled'
- Snapshot Deletion Issues in Trident with ONTAP and CloneSplit Behavior
- Snapshot policy no longer being applied to volumes created through Trident
- SNMP trap related to heartbeat is sent from ONTAP where Trident backend is configured
- Some kubernetes pods fail to mount Trident PV after unexpected reboot on ONTAP
- Some of the trident node pods failed to spin up with the status CrashLoopBackOff
- Stale AMU objects and replicatedSnapshots not being garbage‑collected on target cluster
- storageclass is not supported for AppMirrorRelationship: protocol ‘nfs’ is not supported for ontap-san SnapMirror, must be one of: iscsi, nvme, fcp
- Switching Trident installation methods results in issues with existing PVCs
- TBE delete error: cannot delete backend 'tbe' created using TridentBackendConfig CR; delete the TridentBackendConfig CR first 400 Bad Request
- The container is terminated with “Out of Memory”
- The Helm parameter nodePrep needs to be disabled as affecting the multipath.conf file
- The PVCs are always provisioned on the same zone or SVM
- The trident-csi pods are not rebuilt, erroring on security constraints in Openshift
- The trident pods fails to start after installing the Dynatrace in OpenShift
- The TridentNodeRemediation CR is not recognizing Openshift VM boot disk volumes
- Topology Configuration Not Applying in Kubernetes PVs Ignoring Topology Labels
- Trident's SnapMirror doesn't allow destination read-only access
- Trident-controller keeps restarting due to termination of trident-main container
- trident-controller pod does not start automatically after K8s node unexpectedly stops
- Trident-csi crashloops on invalid snapshot
- trident-main container continuously restart in trident-controller pod due to which daemonset pods failed to communicate to trident CSI controller
- trident-node-linux Pod enters CrashLoopBackOff for minutes after K8s node startup
- Trident-operator incorrectly processes the imageRegistry parameter in the TridentOrchestrator resource
- Trident-pv not mounted on worker node
- TridentBackendConfig is not properly created when using a domain account
- TridentBackendConfig is not properly created/initialized
- Tridentctl command slow with large number of volumes
- 'Tridentctl get backend' times out with exit code 1 with Flexgroup PVC
- tridentctl logs fails with command terminated with exit code 1
- Tridentctl ‘get backend’ Command Timeout and Slow PV Creation in OpenShift/ONTAP Environments
- TridentProtect AMR Destination PVC Fails to Mount: “volume is not read-write” Error
- TridentProtect: Backups and Snapshots Failing with “timeout expired waiting for volume snapshots to be created: permanent error” and Cleanup Issues
- TridentProtect Backups Failing with Kopia Permission Denied
- TridentProtect Backups Stuck in Running State After Upgrade to 25.10
- TridentProtect backup fails with specified key does not exist
- TridentProtect Backup Failure: “kopia volume backup has timed out: progress has not been updated in the allotted time”
- TridentProtect: Failed to promote AMR with error: failed to copy AppArchive: failed to read source's VolumeSnapshots from its AppArchive: The specified key does not exist
- TridentProtect resourceFilter Exclude Ignores Names/LabelSelectors for Secrets
- TridentProtect SnapMirror Relationships Remain in “Establishing” State Due to ONTAP Snapshot Lock/Clone Split Conflicts with NetBackup
- TridentProtect Snapshot Restore Fails with “Existing app definition is different than expected, cannot reuse the application” Error
- Trident's VRQ specification from the backend or the source PVC does not relay to the clone PVC
- Trident - Does Astra Trident Operator modify /etc/iscsi/iscsid.conf on OpenShift?
- Trident - Failed to authenticate
- Trident - how to specify default snapshot policy in backend
- Trident - Kyverno Policy Blocking Trident PV Creation Due to Restricted StorageClass
- Trident - LUN already mapped to initiator(s) in this group error after pod restart
- Trident - OpenShift pods stuck in containerCreating state due to iSCSI session authentication errors
- Trident - Trident Backend Failure due to Service Policy Change on ONTAP
- Trident - Trident OpenShift SCC Patch Conflict Error because of multiple deployments of the Trident operator pod during upgrade
- Trident - unable to delete busy snapshot
- Trident - Unable to provision volumes - backend xxx.xxx.xxx is not Online or Deleting
- Trident 24.10.0 with ontap-nas-economy driver PV access issues on POD restart
- Trident 24.10 upgrade breaks old nas economy qtrees moving to per-qtree
- Trident 25.06.0 ontap-nas-economy is slow on deployments up to ONTAP 9.14.1 Px
- Trident 26.02 concurrency does not allow non-GA backend drivers
- Trident and Capsule compatibility
- Trident and ONTAP Compatibility: Upgrading to ONTAP 9.16.1P10 with Trident v22.10–v23.05
- Trident and OpenShift Container Platform - upgrade order
- Trident AppMirror Replication silently halts and remains stalled
- Trident AttachVolume.Attach Failed for Volume in Trident 25.10
- Trident AttachVolume.Attach failed for volume <PVC-ID> : csinode.storage.k8s.io <node-ID> not found
- Trident auto-forceDetach with Kubernetes 1.24 and Non-Graceful Node Shutdown (NGNS): Risks, Recommendations, and Best Practices
- Trident autoExportPolicy fails to set policy rules and Unix permissions in NAT environment
- Trident Automatic Volume Expansion Fails After Upgrade to v26.02 – “AutogrowRejected” Warnings, No Resize Triggered
- Trident Automatic Volume Expansion Not Triggering as Expected for PVCs
- Trident backed stuck in 'deleting' state and unable to delete it
- Trident BackendConfig Fails to Reconcile After Upgrade Due to Duplicate Backend Name
- Trident backends fail with network is unreachable
- Trident Backends Randomly Going Offline No data lif present
- Trident backend "error initializing ontap-nas-economy driver"
- Trident backend configuration fails when FIPS is enabled
- Trident backend creation failed because of dns resolution
- Trident Backend Creation Fails in OpenShift with “Failed to apply the backend update; problem initializing storage driver ‘ontap-san’”
- Trident backend creation fails with "error dialing backend: remote error: tls: internal error"
- Trident backend creation fails with error dial tcp svm_mgmt_ip:443: connect: connection refused (400 Bad Request)
- Trident backend definition update on MetroCluster switchover and -back made easy
- Trident backend does not properly initialize with ontap version 9.18.1
- Trident backend failed due to port 443 blocked to SVM
- Trident Backend Fails on Azure Government Cloud NoValidSubscriptionsInQueryRequest
- Trident backend failure with error 400 Bad Request
- Trident backend gets offline when configured the user with a domain account
- Trident Backend Gets Stuck in ‘Deleting’ State After Network Switch Swap and VLAN Changes
- Trident backend goes offline and does not recover after controller pod restart
- Trident backend has deleting status after being deleted
- Trident backend initialization failure after migration will not enable CHAP for SVM
- Trident backend in 'failed' status after OCP upgrade
- Trident backend in failed state, cannot communicate with the ONTAP cluster/SVM
- Trident Backend in failed status with error: error reading svm details: 443: connect: no route to host
- Trident backend is in deleting state
- Trident backend is in deleting state blocking existing PV management
- Trident Backend is reported as 'State: offline' with the reason 'SVM is not reachable,' even though there are no network connectivity or certificate issues
- Trident backend not available when doing a switchover in a MetroCluster, when using REST APIs
- Trident Backend Not Finding Storage Class
- Trident backend not presenting the media type from storage class
- Trident backend offline and failing to create new PVC due to 401 incorrect or missing credentials
- Trident backend option 'snapshotReserve' creates larger ONTAP volumes than expected
- Trident backend removal fail with deleting status due to fault volume info
- Trident backend removal remains in deleting state due to volume in same situation
- Trident Backend reporting offline
- Trident backend reporting offline after accidentally deleted the user from ONTAP cluster
- Trident backend update can time out with scaled out PV numbers
- Trident backend update fails with Client.Timeout error
- Trident backups using a third party tool overload the trident-controller pod
- Trident can't be properly upgraded using helm
- Trident Cannot Create DP Volume, Fails with GPRC error no suitable backend file
- Trident can not create the PV volume
- Trident can not differentiate “selector/label” after upgrade
- Trident client rate limiter wait returned an error
- Trident cloned PVCs are sent to the volume recovery queue when deleted
- Trident connection refused when trying to create backend
- Trident complains that it can't delete Snapmirror relationships created by AWS Automatic Backups
- Trident controller and worker nodes to acquire incorrect IP addresses during upgrade
- Trident Controller annotations deleted after OpenShift upgrade despite issue#1004 fix
- trident-controller log shows "Could not obtain aggregate info" error without issues
- Trident controller pod gets overloaded with high amount of PVC mounts
- Trident Controller Pod Initialization Error Due to Unreachable ONTAP Backend
- Trident controller pod logs repeated errors related to VolumeAttachment objects
- Trident Controller Pod Not Receiving IP from NetworkAttachmentDefinition (NAD) on SUSE Harvester
- Trident controller pod restarting frequently
- Trident Controller Pod scales up and down constantly
- Trident controller pod stuck in crashloopbackoff due to error splitting clone
- Trident volume cannot be deleted or resized due to stale tridenttransactions
- Trident creates a new economy ONTAP volume despite space in existing ones
- Trident csi-resizer encounters Out of Memory error during third party backup job
- Trident csi-snapshotter display v3.0.3 version instead of v6.2.1
- Trident CSI Blocked by “Unable to delete snapshot from backend” Errors During OpenShift Virtualization VM Provisioning
- Trident CSI does not detect built-in NVMe/TCP on Talos Linux
- Trident CSI Driver Pods in Unready State After OpenShift and Trident Upgrade
- Trident CSI Fails to Mount Volumes After OpenShift Upgrade to 4.19 – “Could not find iSCSI device: no devices present yet”
- Trident CSI NodeUnstage Failure: iSCSI Session Logout Occurs Before LUN Cleanup
- Trident CSI Operator Installation Failure on OCP 4.21
- Trident CSI pods are missing the storage driver csi.trident.netapp.io
- Trident CSI Topology Awareness not working as expected when the quota limits for a single SVM (TridentBackend) are exceeded
- Trident deletes manually added export-policy rule
- Trident deployed LUN with ontap-san backend causes 'spam' notifications: volume full
- Trident Docker volume creation fails due disabled SSL on SVM
- Trident doesn't create exportPolicy for cloned PV if scheduled to new node
- Trident doesn't match a StorageClass to a CVO or ONTAP Select storage
- Trident does not create an Export Policy for cloned PV if scheduled to a new node
- Trident does not create or update the exportPolicy for cloned PVCs if scheduled to new node
- Trident does not properly initialize after worker nodes were restarted
- Trident does not properly initialize and shows the error "etcdserver: another etcd process is using "//var//etcd//data//member//snap//db" and holds the file lock, or loading backend file is taking >10 seconds"" to "Cloud/Astra/Trident/Trident does not properly initialize and show error
- Trident does not update iSCSI connections when iSCSI LIFs are added to an SVM
- Trident driver takes minutes to start fully after its pod termination (ontap-san)
- Trident Error: “backend is not Online or Deleting” state
- Trident error "client rate limiter Wait returned an error: context canceled"
- Trident error creating backend: entry doesn't exist, Code: 15661 400 Bad Request
- Trident Error during tridentctl import volume
- Trident error in a helm based upgrade "reconcile failed; unsupported Trident image version '24.02.0'"
- Trident error: csi.trident.netapp.io not found in the list of registered CSI drivers
- Trident error: Initiator group (igroup) could not be deleted. Reason: Invalid value specified for \"initiator-group-name\"
- Trident failed to create backend on OCP 4.14 Error: error communicating with Trident REST API
- Trident "failed to create cloned volume pvc-abcdef-123 volume already exists"
- Trident failed to provision volume: post volumes moved across aggregates or new aggregates to SVM with Error code: 14420
- Trident failed to stage volume: failure when reconfiguring multipath
- Trident fails resizing a PVC due to volume size too large for the clone source
- Trident fails to access ONTAP on SVM level and on Cluster level
- Trident fails to attach/mount PVC to the node with multi-attach error
- Trident fails to create new PVC with the error "response code 401 (Unauthorized): incorrect or missing credentials"
- Trident Fails to Create Volumes on ONTAP with SVM-DR Configured
- Trident fails to mount an iSCSI PVC after an ONTAP volume is full
- Trident fails to mount NFSv3 with exit status 32 after upgrade of ONTAP to 9.13.1P8+
- Trident fails to mount PVC due to CSI driver is not found in registered list
- Trident fails to mount PVC with CSI driver is not found in the list of registered
- Trident fails to provision PVCs giving a storageclass not found error
- Trident fails to provision PVC - no available storage for access modes
- Trident fails to provision PVC after aggregate change or removal
- Trident fails to provision storage with: encountered errors in creating the volume
- Trident fails to provision volumes in a timely fashion, leaving pods waiting
- Trident Fails to Start After ONTAP Node Failover Due to TLS Certificate Issue
- Trident fails unstaging PVs on bare metal hosts
- Trident fails volume resize with "unsupported capacity range"
- Trident FSX failing to attach PVC to pod due to locked snapshots
- Trident generates new economy volumes on MCC switchover or switchback
- Trident Helm install fails with: <.Values.imagePullSecrets>: range can't iterate
- In Trident if both nameTemplate is set in the backend and storagePrefix is set in the storageDriver, which one will be used?
- Trident image pulls from docker registry instead of our private registry
- Trident initialization fails due to a PV in the trident repository that cannot be deleted
- Trident Installation Fails on OpenShift Due to ResourceQuota Policy
- Trident Installation fails with error readiness probe failed: HTTP probe failed with statuscode: 503
- Trident install error: failed to create backend: problem initializing storage driver
- Trident install or upgrade unable to validate against any security context constraint
- Trident ISCSI mount fails with error exit status 32: can't read superblock on /dev/mapper/ID
- Trident iSCSI paths do not recover after ONTAP Upgrade
- Trident iSCSI PVCs Created During ONTAP Node Failover Have Only Single Path After Giveback
- Trident is slow in PVC creation when multiple PVCs are requested
- Trident is unable to create a clone with a PVC involved with an SVM-DR relationship
- Trident is Unable to delete snapshot from backend, causing PVC to hang in terminating
- Trident leaves empty economy pool volumes behind
- Trident Leaves Orphaned iSCSI Multipath Devices and Stale Mounts After Pod Detach
- Trident leaves POD in ContainerWaiting for provisioning ANF NFS PVs
- Trident logs error: Failed to add portal to self-healing map; err: portal value cannot be empty
- Trident logs error: TLS handshake error from IP:51792: read tcp IP:17546-IP:51792: read: connection reset by peer
- Trident Misidentifies Filesystems on LUKS Devices Due to blkid
- Trident mount error: code = Internal desc = unable to mount device; exit status 32
- Trident mount volume failed with the error "context deadline exceeded"
- Trident nameTemplate not applied for OpenShift Virtualization VM disks created from CDI VolumeCloneSource
- Trident nas-economy and san-economy drivers do not have the option to import ontap volumes
- Trident newly created pods are unable to be mounted due to mount failure exit 32
- Trident NFS export rules deleted after controller restart
- Trident NFS mount.nfs: mount(2): Permission denied while trying to mount volume on pod
- Trident NFS Volume Mount Fails with MountVolume SetUp failed for volume exit status 32 due to Delayed Export Policy Reconciliation
- Trident Node Pod Fails to Start Due to Corrupted Container Image trident orchestrator: no such file or directory
- Trident node reporting errors about PV
- Trident not preserving existing annotations after update from v26.02.0 to v26.02.1
- Trident NVMe backend errors with "hostNQN not found"
- Trident NVMe devices of type RWO are visible on multiple nodes
- Trident NVMe PVC clone failures after upgrade to 26.02/26.06
- Trident NVMe volumes not cleaned up after ingest jobs
- Trident NVMe volumes not mounting due to mismatched MTU in path
- Trident ONTAP-NAS drivers are failing to mount volumes
- Trident ontap-san PVs mounts take a long time or exceed the node attach deadline
- Trident ontap-san PV creation is slow on large PVCs during formatting
- Trident ONTAP NAS NFS4 PV's are mounting but access is denied to application
- Trident ONTAP-SAN driver cannot find multipath device after node upgrades, failing PV
- Trident OpenShift install images from docker.io errors with manifest unknown
- Trident OpenShift Upgrade produces error - chown, chmod or applyFSGroup failed, permission denied
- trident-operator fails to start with "/trident-operator: no such file or directory"
- Trident Operator warning messages for unknown CRD fields after upgrade to 26.02
- Trident Orchestrator crash looping due to non existing volume
- Trident Orchestrator CR pod missing
- Trident orchestrator failed with message: Failed to detect installed Trident resources; err: failed to initialize Kubernetes client
- Trident Persistent Volume Attachment Errors in Kubernetes with Velero Kopia Backups
- Trident placement issue using wrong SVM
- Trident pods are not created for windows nodes, when Trident is deployed in an OpenShift cluster
- Trident pods can't be properly scheduled in kubernetes nodes, in a new installation
- Trident Pods CrashLoopBackOff and Rubrik Failures due to Network policy
- Trident pods fail to run on OpenShift cluster nodes with specific labels and defaultNodeSelector specified on the scheduler
- Trident pods get stuck in ContainerCreating status, after upgrading the OpenShift version
- Trident pods in CrashLoopBackOff when doing the Trident deployment
- Trident pods show CrashLoopBackOff or ImagePullBackOff after redeployment
- Trident pod in crashloopbackoff status after Trident upgrade
- Trident pod is stuck in a crashloopbackoff state and is unable to be used
- Trident pod on a worker node fails with error : Readiness probe failed: HTTP probe failed with statuscode: 503
- Trident Pod Security Policies with K8s 1.25
- Trident Protect application backups fails with non-trident PVs with Name is Required
- Trident Protect backups not deleted in Ontap S3
- Trident Protect backup fails with could not find qtree after storagePrefix change
- Trident Protect backup fails with "insufficient storage available in the Vserver"
- Trident Protect Backup to NetApp S3 Stores Only Metadata (No VM/PVC Data)
- Trident Protect gets the error unknown field spec.resourceFilter
- Trident Protect not deleting snapshots in storage
- Trident Protect SnapMirror Relationship Remains Uninitialized Due to Incorrect SVM Peering Configuration
- Trident Protect upgrade or uninstall fails due to no deployed releases
- Trident: Provisioning storage on OpenShift cluster fails with "Context deadline exceeded"
- Trident PVCs only mounted using one data lif
- Trident PVCs Volumes Created on Wrong Aggregate
- Trident PVC attach failure in OpenShift with FC: “no matching WWPN found for node”
- Trident PVC can't be properly created and bound, when using the parameter "csi.storage.k8s.io/fstype" in a storage class
- Trident PVC create error: Unknown desc = no available backends for storage class
- Trident PVC creation failed with error Unknown desc = no available backends for storage class
- Trident PVC creation fails with "Ruleset not found"
- Trident PVC creation using ONTAP-SAN Storage Class stuck in pending state
- Trident PVC deployment fails with topology set on worker nodes
- Trident PVC fails to mount due to could not find tracking file after pod movement
- Trident PVC fails to mount with error: node is already present in another initiator group and both initiator groups share a LUN ID
- Trident PVC mount error: did not read 4KiB bytes from device, instead read 4199 bytes
- Trident pvc mount fails with mount.nfs: Connection timed out
- Trident PVC received Multi-Attach error after power outage in data center
- Trident PVs get into read-only mode when full
- Trident PV creation fails on ONTAP SVM with “Insufficient storage available in the Vserver”
- Trident PV creation shows PVC stuck in pending status
- Trident PV FailedAttachVolume with NVMe zeroes named namespace
- Trident Qtree async delete - Failed to load job for Delete qtree
- Trident removes original PVs NFS export on ontap-nas-economy PVs on clone unpublish
- Trident resize operation on a FlexGroup does not complete
- Trident responds slowly in ONTAP operations seeing TLS Handshake issues on ONTAP
- Trident retried locked snapshot delete, clone split still running
- Trident RWX PVC can't be mounted in a worker node and getting error "error saving volume publication record"
- Trident RWX Support Over FC: Can Filesystem Volume Mode Be Used with RWX Access in OpenShift?
- Trident second PV SAN deployment fails with igroup already contains initiator
- Trident seems to require ontapi application on SVM accounts for ONTAP 9.14.1
- Trident showing routes as failed faulty running on large volumes
- Trident slow Volume Attachment after Data Center Failover
- Trident SMB PVC connection actively refused
- Trident snapshots fail occassionally for ontap-san-economy driver
- Trident Snapshot performance during PVC create/delete
- Trident software reports "volume not found" error prematurely during clone operations
- Trident spams notifications that volume is full
- Trident StorageClass “netapp-default” Stuck in Terminating State Blocks Provisioning
- Trident's CSI support changed the previously practical volume naming scheme
- Trident's PV volume count and Kubernetes PV counts are different
- Trident transient pod is not created during install
- Trident unable to create a TridentBackendConfig (TBC) due to a timeout with both Rest API and ZAPI
- Trident unable to create a Trident backend using the flex serviceLevel with the google-cloud-netapp-volumes driver
- Trident Unable to Delete CommVault Snapshots on ONTAP Volumes with SVM-DR Protection
- Trident unable to delete snapshots - skipRecoveryQueue not applied to existing PVCs
- Trident Unable to find API: system-node-get-iter, Code: 13005
- Trident unable to mount NFS volumes
- Trident unable to populate media type for aggregates when using REST API
- Trident unable to update export policies after upgrade to 24.06.1
- Trident update backend failure - 400 Bad Request
- Trident upgrade errors with "<trident_ver> is an unsupported Kubernetes version"
- Trident upgrade from 19.01 to 20.07 failed with missing volume
- Trident upgrade from 25.06 to 25.10 does not complete
- Trident upgrade gets stuck and not progressing
- Trident upgrade or install fails with libdl.so.2 cannot open shared object file
- Trident Upgrade shows "Linux Only" from Rancher GUI
- Trident uses default export policy when autoExportPolicy is set to 'false'
- Trident uses the wrong NFS DATA LIF to mount the PVC
- Trident VolumeSnapshots Remain in “Not Ready” State on RKE2
- Trident volumes and VolumeSnapshots stuck after backup
- Trident volumes are not removed even when associated PV and PVC are properly deleted in the OpenShift cluster
- Trident volumes are not showing up anymore and can't be mounted by applications
- Trident Volumes failing to mount due to export policy configuration
- Trident volumes get full because snapshots invade ontap volume's data area
- Trident Volumes Remain in Released State and Aggregate Volume Count Reaches Maximum Limit on NetApp ONTAP
- Trident volumes stuck in deleting state after OpenShift Virtualization VM deletion
- Trident Volumes “Deadline Exceeded” Error During VM Migration in OpenShift
- Trident Volume Attach Fails with could not find volume with name After Cross-Cluster Import and Volume Rename
- Trident Volume Cloning Fails Across Different Storage Classes After Upgrade
- Trident volume creation fails after Trident upgrade
- Trident volume import operation fails with no available backend error
- Trident volume mounts are slow after changing from NFSv3 to NFSv4.1
- Trident volume provisioning failed with error: failed to provision volume with StorageClass "StorageClass": rpc error: code = Unknown desc
- Trident volume provisioning fails with 'no available backends for storage class'
- Trident volume remains in a "deleting" state after PVC is deleted
- Trident warning "Volume publication record not found, returning success"
- Trident with Commvault backups triggers unexpected clone splits in ONTAP
- Trident with openshift and NAS-ONTAP fails to create backend
- Trident worker nodes unable to mount PV after maintenance
- Trident: "Multipath device not found"
- Trident: PVC not bound after RHEV to OpenShift migration
- Trident: Unable to mount volume on Pod with "iSCSI login error: exit status 6"
- Trident Veeam Kasten only has 1 snapshot available
- VMs hang in OpenShift during mkfs.xfs on large disks
- Trying to install Trident-Protect on pods fails with CA certificate error
- Unable to Attach Persistent Volume Claim (PVC) Using Trident – “nomatching WWPN found for node” Error
- Unable to Create a Trident Backend Configuration Using Certificate Based Authentication
- Unable to create backend - deferred syncing TridentBackendConfig
- Unable to Create PVC in OpenShift Cluster Using NetApp Trident: “Cannot provision volume on root aggregate” Error
- Unable to create RWX PVCs
- Unable to create snapshots: snapshots cannot be taken if snapdir access is disabled
- Unable to Delete Kubernetes Volume Snapshots on ONTAP – “Busy/Locked” Errors with Trident CSI
- Unable to delete TridentBackendConfig and cannot delete related trident volumes
- Unable to deploy Trident Worker nodes with IPv6
- Unable to download csi-resizer v1.13.0
- Unable to mirror the NetApp Trident Operator images in an air-gapped OpenShift environment due to missing signatures
- Unable to Mirror Trident Operator 25.10 to Internal Registry with oc-mirror
- Unable to Mount iSCSI PVCs with Trident Due to find_multipaths = yes
- Unable to mount iSCSI volumes
- Unable to Mount Persistent Volume Claim (PVC) Using NetApp Trident – “nomatching WWPN found for node” Error
- unable to mount PVC - context deadline exceeded
- Unable to mount PVC due to Kubernetes namespace error
- Unable to Provision GCNV Flex PVCs via Trident – “no GCNV storage pools found for Trident pool” Error
- Unable to provision PVCs when REST is enabled
- Unable to provision PVC due to expired or no SSL certificate on SVM
- Unable to Pull Trident Images From registry.k8s.io Due To connection reset by peer Error When Accessing Google Artifact Registry
- Unable to remove orphaned Docker volumes
- Unable to unstage volumes in OCP cluster due to a multipath device not being flushed
- Unable to use Trident after using default endpoints in AWS
- Unlike new PVs created, imported volume do not create an InternalID reference
- unsupported configuration; updating the storage prefix isn't currently supported
- Upgrading Trident deletes connectivity when using a dedicated network
- Upgrading Trident Helm installation using private registry fails with RBAC error
- User State Showing as Unknown After ONTAP Upgrade on Trident Backend
- Using fsGroup on RWX PVs does not work with Trident in default setup
- Using single StorageClass with zone topology doesn't appear to work with Trident
- Using third party Backup in Trident Kubernetes Cluster causes PVC creation timeouts
- Using Trident to create a TBC for existing backend fails with configRef error
- Veeam Kasten restore fails to create a PVC
- Very low transfers when uploading qcow2 images to Trident PVCs using Kubevirt CDI
- VMs Enter Paused State Due to I/O Errors on RWX PVCs During OpenShift Upgrade
- VM clone in Kubevirt fails to be created in a kubernetes cluster
- VM freezes due to space contraints on PVC on an image created Windows 11 system
- Volumesnapshots are not correctly created with Astra Trident
- VolumeSnapshot used to create a new Trident PVC, can't be deleted
- Volumes Unmounted Automatically After Server Reboot When Using Trident Auto Export Policy
- Volume creation fails due to unsupported unencrypted volumes in NetApp Aggregate Encryption (NAE) aggregates
- Volume creation fails with error "checking for existing volume"
- Volume mount fails with the error "failed to stage volume: multipath device 'dm-xx' serial check failed"
- Volume operations getting queued and fails to perform the mount operation
- Volume remains on storage after deleting PVC with kubectl
- Volume size and quotas remain after PVC and qtree deletion
- What are functional differences of Trident ontap-san and ontap-san-economy drivers?
- What are these Trident ports used for?
- What are the best practices for increasing the filesystem size backing a Kubernetes Persistent Volume (PV) (ext4 or XFS) when using the Trident CSI Driver?
- What are the minimum Permissions needed for Trident Admin Users when using a SolidFire Backend?
- What are the minimum required S3 bucket permissions to support Trident Protect AppVaults?
- What container images and tags are needed to install Trident 25.06.2?
- What does the "cleanable" state in Trident mean?
- What FlexVol does Trident create a new LUN in when using ontap-san-economy?
- What is the default value of the k8sAPIQPS/--k8s_api_qps parameter in Trident version 25.06?
- What is the difference between Trident AutoSupport and ONTAP AutoSupport?
- What is the impact of changing dataLIF or managementLIF on the trident backend?
- What is the purpose of the denyNewVolumePools option
- What is Trident's compatibility with the ONTAP 9 versions ?
- What operations are executed when nodePrep: [iscsi] is set for Trident on OpenShift?
- What options can be used for Trident Orchestrator with OpenShift OperatorHub?
- What port is used between Trident and the IP address of the Management LIF?
- What's the best practice for Trident backend configuration
- What Trident backend configuration is required for creating NVE and NAE volumes
- What Trident pods are LogLevel and Debug options specified in values.yaml for?
- When creating a backend getting warning failed to create backend
- When migrating VMs to a different worker node in an OpenShift cluster, it takes 5 minutes to boot up properly
- When using Trident, is it necessary to configure iSCSI and multipath on Kubernetes master nodes as well as worker nodes?
- Where are definitions of Trident metrics available?
- Where are the mount options for Persistent Volumes specified?
- Whether Netapp Trident supports multiple data-path IPs and automatic NAS data LIF failover
- Which backends are supported by Astra Trident?
- Which filesystem is recommended, ext4 or XFS, for the Trident CSI driver Persistent Volumes?
- Which of the two Trident Operator 25.10.0 should be installed on OpenShift?
- While running tridentctl get node command NVMe service is not visible on node
- Why doesn’t Trident rename ONTAP FlexGroup volume and junction path during managed volume import?
- Why does cloned PVCs retain source backend despite specified StorageClass?
- Why does Trident continuously create and delete volumes on ONTAP when a PVC is stuck in Pending state due to a backend QoS configuration error?
- Why has my ONTAP backend reached its volume limit even though Trident reports fewer volumes in use?
- Why VM Names from RHVM Are Not Preserved in PVCs During Migration to OpenShift
- Trident worker Nodes Fail to Mount NVMe/TCP Volumes After ONTAP Cluster Expansion
- Zombie processes on linux nodes causing Trident pod to be stuck 'Terminating'