Skip to main content
NetApp Knowledge Base

Trident - Trident Backend Failure due to Service Policy Change on ONTAP

Views:
50
Visibility:
Public
Votes:
0
Category:
trident-openshift
Specialty:
snapx
Last Updated:

Applies to

Astra Trident

Issue

The Trident backend is in a failed state. The error message indicated that the backend was not available.

Trident Controller log:

time="2025-08-02T15:09:47Z" level=error msg="Could not unpublish volume." 
error="<backend_name> is not Online or Deleting" logLayer=csi_frontend node=<node_name> requestID=xxxxxxxxx 
requestSource=CSI volume=<pvc_name> 
workflow="controller=unpublish"

ASUP log:

<Cluster> :: network interface service-policy add-service -policy custom-data-15972 -service management-https -vserver <vserver_name> :: Pending 
00000027.0024afcb 00b5641a Sat Aug 02 2025 18:23:58 +05:30 [kern_audit:info:3720] 8003e80000086575:8003e80000086925:: <IP_Address :: \v1001303 :: network interface service-policy add-service -policy custom-data-15972 -service management-https -vserver <vserver_name> :: Success 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.