Skip to main content
NetApp Knowledge Base

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?

  1. Last updated
  2. Save as PDF
Views:
78
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

Applies to

NetApp Trident

Description

  • This is expected behavior. When a PVC is created, Trident attempts to provision a volume on ONTAP.
  • If the QoS configuration in the backend is incorrect, the volume creation fails, and Trident immediately deletes the volume.
  • Since the PVC isn’t deleted, Kubernetes keeps retrying, causing Trident to repeatedly create and delete volumes.
  • If ONTAP volume recovery is enabled, these deleted volumes accumulate, potentially reaching the volume limit.

 

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.