Skip to main content
NetApp Knowledge Base

Automatic Volume Expansion Not Working After Upgrade to Trident 26.02

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

Applies to

  • NetApp Trident v26.02
  • Kubernetes clusters using Trident
  • ONTAP backends (e.g., AFF-C60)
  • Automatic Volume Expansion (autogrow) feature

Issue

Automatic volume (LUN) expansion was not working in a Kubernetes cluster using Trident 26.02, despite correct configuration of allowVolumeExpansion and autogrowPolicy in the StorageClass. Volumes did not automatically grow when utilization thresholds were crossed.

Log Output and Observed Behavior:

  • No errors related to autogrow in Trident controller logs.
  • unknown field” warnings in Trident controller log.
  • TVP (TridentVolumePublication) CRDs missing fields such as autogrowPolicy, storageClass, backendUUID, and pool.
  • Existing TVP objects did not contain autogrow-related fields, causing the autogrow scheduler to ignore configured policies.

level=debug msg="Syncing volume publications" logLayer=core requestID=dabd4f17-1d1d-4533-9511-d562095cec78 requestSource=Internal vpsRemaining=1 vpsTotal=184 workflow="core=bootstrap"
level=debug msg=">>>>>> syncVolumePublications" logLayer=core nodeName=<node name> requestID=dabd4f17-1d1d-4533-9511-d562095cec78 requestSource=Internal volumeName=pvc-uuid workflow="core=bootstrap"
I0420 13:20:27.353816       1 warnings.go:107] "Warning: unknown field \"backendUUID\""
I0420 13:20:27.353839       1 warnings.go:107] "Warning: unknown field \"pool\""
I0420 13:20:27.353844       1 warnings.go:107] "Warning: unknown field \"storageClass\""

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.