#Looks like trident finds it hard to connect to 9.15.1 system when using vsadmin.

1 messages · Page 1 of 1 (latest)

livid cave
#

The message is:
level=error msg="Could not obtain aggregate info; storage classes with physical attributes such as 'media' will not match pools on this backend: could not retrieve aggregate information." crdControllerEvent=add logLayer=core

Same setup on 9.14.1P5 works fine.

sharp fulcrum
#

strange that this seems to have worked before; a vsadmin user cannot see physical properties of the aggregate at all... the whole storage subcommand tree is unavailable to them. If it worked, I assume it was a bug which has been fixed?

livid cave
#

Works even now on 9.14 and previous versions. But if it is not supposed to work, then vsadmin is not viable option for trident and ontap?

#

It is in the documentation though, so let's bring vsadmin back on the menu..

sharp fulcrum
#

vsadmin works, yes, but there are limitations for example you cannot use the "aggr capacity limit" (or whatever it's called) because a vsadmin cannot see the aggregates. I assumed it is the same for the disk type, but I could be wrong though

livid cave
#

Out of curiosity, what is the recommended approach? Go for cluster admin or vsadmin?

#

just found this in documentation:
useREST - true for ONTAP 9.15.1 or later, otherwise false - that explains a lot.

sharp fulcrum
#

we always use SVM users (vsadmin). You can do the whole storage selection in k8s (i.e. add tags to the backend and the appropriate selector to the StorageClass) unless you have multiple clusters with the same disks that you want to all use for Trident

livid cave
#

Prolly pointless to have media: ssd when talking to AFF too....