Skip to main content
NetApp Knowledge Base

Trident PVCs Volumes Created on Wrong Aggregate

Views:
5
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

  • Trident
  • Trident NAS and SAN backends
  • Environments with multiple ONTAP aggregates/backends

Issue

  • Persistent Volume Claims (PVCs) created via Trident are being provisioned on the wrong ONTAP aggregate (e.g., aggr01 instead of intended aggr02), even when the aggregate parameter is specified in the Trident backend configuration.
  • Existing NAS volumes remain accessible after aggregate changes, but new PVCs do not get created in the desired aggregate.
Relevant Trident Log Output:
time="2026-05-18T12:28:25Z" level=debug msg="Result of pool match for storage class." attributesMatch=false logLayer=core match=false pool= aggr02 poolsMatch=true requestID=... storageClass=test-nas-altiplanodr workflow="storage_class=create"
time="2026-05-18T12:28:25Z" level=debug msg="Result of pool match for storage class." attributesMatch=false logLayer=core match=false pool= aggr01 poolsMatch=true requestID=... storageClass=test-nas-altiplanodr workflow="storage_class=create"

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.