Trident + nvmeoe setup

[jolly cradle]

trident 24.06 + ontap 9.16.1P11.

Creating nvme san backend with svm level user. Succesful but storage class is not synced.

time="2026-03-16T19:18:18Z" level=warning msg="Could not determine controller serial numbers. [GET /cluster/nodes][403] nodes_get default  &{Error:0xc00222fad0}" logLayer=core requestID=26434ac0-229b-4324-8449-b21af6bf318e requestSource=REST workflow="backend=create"
time="2026-03-16T19:18:18Z" 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." logLayer=core requestID=26434ac0-229b-4324-8449-b21af6bf318e requestSource=REST workflow="backend=create"```

So lets create the role: 

```netapp-aff-::> security login rest-role create -role "trident" -api "/api/cluster/nodes" -access readonly   -vserver cut-name

Error: command failed: A Vserver admin cannot use command directory "system node" with access level "readonly". Use a different access level.

So only option is to use cluster scope user?

Another error is related to https://kb.netapp.com/Cloud/Astra/Trident/Trident_unable_to_populate_media_type_for_aggregates_when_using_REST_API

Any updates in regards to TRID-17218?

Thanks.

[river elm]

That's a REST issue that should be fixed in a future version of Trident. You can either ignore it, if it isn't causing problems, or set "useREST: false" in the backend and go back to ZAPI calls.

[jolly cradle]

Ok, going forward.

time="2026-03-16T20:44:49Z" level=error msg="GRPC error: rpc error: code = Unknown desc = encountered error(s) in creating the volume: [Failed to create volume pvc-2ce7ddbc-2fbc-4c55-96a0-f037f6a4b9f2 on storage pool netapp_aff_dc6_213_u26_01_SSD_CAP_1 from backend backend_nvme_netapp_waw_05_dev_dc6: backend cannot satisfy create request for volume trident_pvc_2ce7ddbc_2fbc_4c55_96a0_f037f6a4b9f2: (ONTAP-NVMe pool netapp_aff_dc6_213_u26_01_SSD_CAP_1/netapp_aff_dc6_213_u26_01_SSD_CAP_1; error creating NVMe Namespace trident_pvc_2ce7ddbc_2fbc_4c55_96a0_f037f6a4b9f2: ZAPI call is not supported yet)]" logLayer=csi_frontend requestID=9861729c-ead2-4dfc-b868-24f33e2342ed requestSource=CSI

Reading docs :

NVMe is supported only with ONTAP REST APIs and not supported with ONTAPI (ZAPI).

heh, the trick - edit backend after creation 🙂