Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 86 results
    • After restoring the etcd database, Trident plugin does not properly start
      https://kb.netapp.com/Cloud/Astra/Trident/After_restoring_the_etcd_database_Trident_plugin_does_not_properly_start
      Applies to NetApp Astra Trident 19.X NetApp ONTAP 9.X Issue After restoring etcd database Trident does not properly boot with the error: Liveness probe failed: Error: could not get backends: Trident i...Applies to NetApp Astra Trident 19.X NetApp ONTAP 9.X Issue After restoring etcd database Trident does not properly boot with the error: Liveness probe failed: Error: could not get backends: Trident initialization failed; error attempting to clean up volume customer_volume_name from backend trident_backend_name: error destroying volume : API status: failed, Reason: Volume name: The first character must be a letter or underscore., Code: 13001 (500 Internal Server Error)
    • Trident provisioned LUN turns offline due to volume full and filesystem goes 'read-only'
      https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/Trident_provisioned_LUN_turns_offline_due_to_volume_full_and_filesystem_goes_'read-only'
      level=warn ts=<time> caller=grpc_logging.go:76 method=/logproto.Pusher/Push duration=234.509µs msg=gRPC err="create new segment file: open <filepath>: read-only file system" Data ONTAP sends an alert ...level=warn ts=<time> caller=grpc_logging.go:76 method=/logproto.Pusher/Push duration=234.509µs msg=gRPC err="create new segment file: open <filepath>: read-only file system" Data ONTAP sends an alert that a Trident volume (ontap-san backend) is full The volume and LUN are provided by Trident automatically according to below rule:
    • How to update Trident with changed credential of Storage back end (ONTAP)
      https://kb.netapp.com/Cloud/Astra/Trident/How_to_update_Trident_with_changed_credential_of_Storage_back_end_ONTAP
      Applies to Trident Description This article describes how to update Trident to reflect changed credentials on the NetApp Storage. When credentials of back end storage is changed, the Trident backend.j...Applies to Trident Description This article describes how to update Trident to reflect changed credentials on the NetApp Storage. When credentials of back end storage is changed, the Trident backend.json should be updated with this new credential.
    • Astra Trident debugging not enabled
      https://kb.netapp.com/Cloud/Astra/Trident/Astra_Trident_debugging_not_enabled
      Applies to NetApp Astra Trident Enable Trident debugging Issue After enabling the debugging in Trident, the logs do not properly show debugging traces
    • Error initializing ontap-nas driver when creating a Trident backend
      https://kb.netapp.com/Cloud/Astra/Trident/Error_initializing_ontap-nas_driver_when_creating_a_Trident_backend
      When creating a Trident backend the following errors are provided: time="YYYY-MM-DDTHH:MM:SSZ" level=error time="YYYY-MM-DDTHH:MM:SSZ" level=error msg="Could not initialize error="error initializing o...When creating a Trident backend the following errors are provided: time="YYYY-MM-DDTHH:MM:SSZ" level=error time="YYYY-MM-DDTHH:MM:SSZ" level=error msg="Could not initialize error="error initializing ontap-nas driver: could not create Data ONTAP API client: error creating ONTAP API client: error reading SVM details: Post \"https://XX.YY.ZZ.XX/servlets/netapp.servlets.admin.XMLrequest_filer\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
    • Trident upgrade from up to version 19.04 to 19.07 or later fails to migrate the volume metadata
      https://kb.netapp.com/Cloud/Astra/Trident/Trident_upgrade_from_up_to_version_19.04_to_19.07_or_later_fails_to_migrate_the_volume_metadata
      Applies to Trident 19.07 or higher Issue During upgrade, with the etcd image started under the new Trident version, the following error appears, effectively not migrating the metadata into CRDs: level...Applies to Trident 19.07 or higher Issue During upgrade, with the etcd image started under the new Trident version, the following error appears, effectively not migrating the metadata into CRDs: level=warning msg="Couldn't retrieve volume transaction logs: Unable to find key"
    • Trident controller log gets spammed with trace "Trident-ACP version is empty"
      https://kb.netapp.com/Cloud/Astra/Trident/Trident_controller_log_gets_spammed_with_trace_Trident_ACP_version_is_empty
      Applies to NetApp Astra Trident 23.10 Kubernetes/OpenShift cluster Issue After upgrading to Astra Trident 23.10, the trident-controller shows the following traces every some seconds: time="YYYY-MM-DD ...Applies to NetApp Astra Trident 23.10 Kubernetes/OpenShift cluster Issue After upgrading to Astra Trident 23.10, the trident-controller shows the following traces every some seconds: time="YYYY-MM-DD Thh:mm:ssZ" level=error msg="Trident-ACP version is empty." error="<nil>" logLayer=rest_frontend requestID=xxxxxxxx-yyyy-zzzz-tttt-yzyzyzyzyzzy requestSource=REST workflow="core=version"
    • Volumesnapshots are not correctly created with Astra Trident
      https://kb.netapp.com/Cloud/Astra/Trident/Volumesnapshots_are_not_correctly_created_with_Astra_Trident
      Applies to NetApp Astra Trident 23.01.1 NetApp ONTAP 9.X Volumesnapshots are using API v1 Issue When creating volumesnapshots in a Kubernetes cluster, they get stuck with the following events: Events:...Applies to NetApp Astra Trident 23.01.1 NetApp ONTAP 9.X Volumesnapshots are using API v1 Issue When creating volumesnapshots in a Kubernetes cluster, they get stuck with the following events: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal CreatingSnapshot 6m20s snapshot-controller Waiting for a snapshot namespace/volumesnapshotname to be created by the CSI driver
    • Trident backend creation failed because of dns resolution
      https://kb.netapp.com/Cloud/Astra/Trident/Trident_backend_creation_failed_because_of_dns_resolution
      Request Method: POST Request URL: http://127.0.0.1:8000/trident/v1/backend Request headers: map[Content-Type:[application/json]] Request body: {"aggregate":"aggr_prod","backendName":"prod-backend","da...Request Method: POST Request URL: http://127.0.0.1:8000/trident/v1/backend Request headers: map[Content-Type:[application/json]] Request body: {"aggregate":"aggr_prod","backendName":"prod-backend","dataLIF":"k8sprod-data.example.coml","defaults":{"exportPolicy": "exportprodmi","spaceReserve":"volume"},"limitVolumeSize":"10Gi","managementLIF":"k8sprodmi-mgmt.example.com","password":"....", "storageDriverName":"ontap-nas","storagePrefix":"trident_","username":"vsadmin","version":1} ..............…
    • 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
    • Trident's PV volume count and Kubernetes PV counts are different
      https://kb.netapp.com/Cloud/Astra/Trident/Trident_s_PV_volume_count_and_Kubernetes_PV_counts_are_different
      Applies to Trident Kubernetes Trident's PV volume count and Kubernetes PV counts are different kubectl get pv | grep standard | wc -l tridentctl -n trident get volumes | grep standard | wc -l