Skip to main content
NetApp Knowledge Base

Trident Pods CrashLoopBackOff and Rubrik Failures  due to Network policy

  1. Last updated
  2. Save as PDF
Views:
3
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
cloud
Last Updated:

Applies to

  • NetApp Trident (CSI driver)
  • NetApp ONTAP 9.17.1P2
  • OpenShift 4.19.x / Kubernetes 1.32.x
  • Rubrik backup integration with Trident-managed PVCs

Issue

Rubrik backups of the mas-masprd-core namespace failed on Trident-managed PVCs. Multiple Trident node pods were stuck in CrashLoopBackOff state, with pod logs showing readiness probe failures:

Readiness probe failed: HTTP probe failed with status code: 503

Sample pod status:

trident-node-linux-5jr6f   0/2   CrashLoopBackOff   ...trident-node-linux-69lhc   0/2   CrashLoopBackOff   ......

Additionally, numerous pending and successful DELETE operations for snapshots were observed on the relevant volumes. Rubrik was unable to complete backups due to these Trident pod failures.

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.