Trident PVCs Volumes Created on Wrong Aggregate
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"