We are testing some functionality in the new REST API, and I have been having issues with updating volume comments on a couple filers. Filers I have tested on are running: NetApp Release 9.7P11D1: Wed Jan 27 17:40:19 UTC 2021 NetApp Release 9.7P8: Thu Oct 15 04:11:57 UTC 2020 NetApp Release 9.8P4: Mon May 03 09:22:00 UTC 2021 I suspect there is some issue with the job control in some way, but I have not been able to verify. Have poked around in logs in systemshell as well as checked 'job history show' for any clues. I submitted a case to Support and they suggested I ask here.   The program I am using to do the updates: import netapp_ontap from netapp_ontap import config, HostConnection, NetAppRestError, utils from netapp_ontap.resources import Svm, Volume, Aggregate, VolumeMetrics, Cluster, Node, CLI from pprint import pprint as pp import logging logger = logging.getLogger() logger.setLevel(logging.DEBUG) ch = logging.StreamHandler() ch.setLevel(logging.DEBUG) logger.addHandler(ch) utils.DEBUG = 1 utils.LOG_ALL_API_CALLS = 1 naauth = {'username': <USER> , 'password': <PASS>} admin = <FILER> with HostConnection(admin, verify=False, **naauth): netapp_ontap.host_connection._HOST_CONTEXT.port=<PORT> resource = Volume(uuid='dbdccb94-c936-11eb-b0cb-00a098ce3ae6') resource.comment = "testingacomment" result = resource.patch() if result.is_err: logger.error(f"Volume Comment Update Failed - {result.http_response.status_code} - {result.http_response.reason}")   The Responses from the API: -----------REQUEST----------- PATCH https://[filer]:[port]/api/storage/volumes/dbdccb94-c936-11eb-b0cb-00a098ce3ae6 User-Agent: python-requests/2.26.0 Accept-Encoding: gzip, deflate Accept: */* Connection: keep-alive X-Dot-Client-App: netapp-ontap-python-9.9.1.0 Content-Type: application/json Content-Length: 30 b'{"comment": "testingacomment"}' ----------------------------- -----------RESPONSE----------- 202 Accepted Date: Tue, 07 Sep 2021 16:22:57 GMT Server: libzapid-httpd X-Content-Type-Options: nosniff Cache-Control: no-cache,no-store,must-revalidate Content-Length: 189 Content-Type: application/hal+json Keep-Alive: timeout=5, max=100 Connection: Keep-Alive { "job": { "uuid": "dccd0527-0ff7-11ec-bbe3-00a098ef3e3a", "_links": { "self": { "href": "/api/cluster/jobs/dccd0527-0ff7-11ec-bbe3-00a098ef3e3a" } } } } ------------------------------ https://[filer]:[port] "GET /api/cluster/jobs/dccd0527-0ff7-11ec-bbe3-00a098ef3e3a?fields=message%2Cstate HTTP/1.1" 200 220 -----------REQUEST----------- GET https://[filer]:[port]/api/cluster/jobs/dccd0527-0ff7-11ec-bbe3-00a098ef3e3a?fields=message%2Cstate User-Agent: python-requests/2.26.0 Accept-Encoding: gzip, deflate Accept: */* Connection: keep-alive X-Dot-Client-App: netapp-ontap-python-9.9.1.0 None ----------------------------- -----------RESPONSE----------- 200 OK Date: Tue, 07 Sep 2021 16:22:58 GMT Server: libzapid-httpd X-Content-Type-Options: nosniff Cache-Control: no-cache,no-store,must-revalidate Content-Length: 220 Content-Type: application/hal+json Keep-Alive: timeout=5, max=99 Connection: Keep-Alive { "uuid": "dccd0527-0ff7-11ec-bbe3-00a098ef3e3a", "state": "failure", "message": "entry doesn't exist", "_links": { "self": { "href": "/api/cluster/jobs/dccd0527-0ff7-11ec-bbe3-00a098ef3e3a" } } } ------------------------------ Job (failure): entry doesn't exist. Timeout remaining: 30. ... View more

I found what seems to be a mapping API call on the swagger doc to turn on/off storage efficiency.      https://library.netapp.com/ecmdocs/ECMLP2876964/html/index.html#/storage/volume_modify    Would this API call cover the turn on/off part too ?      ... View more

We are facing one strange issue. For some reason, we are not getting volume’s details through REST API. For example, we have these 2 volumes in the cluster running 9.7P10: us01cmsgrid::> vol show VG_ARCHIVE*                      Vserver   Volume       Aggregate    State      Type       Size  Available Used% --------- ------------ ------------ ---------- ---- ---------- ---------- ----- us01cmsgridvs1 VG_ARCHIVE -         online     RW        100TB    15.74TB   84% us01cmsgridvs1 VG_ARCHIVE2 -        online     RW        100TB    69.79TB   30% 2 entries were displayed.   They are set up identically.   But when we make API call, only VG_ARCHIVE2 is showing up: $ curl --location --request GET 'https://us01cmsgrid/api/storage/volumes' -k | grep -i "VG_ARCHIVE" "name": "VG_ARCHIVE2",   $ curl --location --request GET 'https://us01cmsgrid/api/storage/volumes?name=VG*' -k {   "records": [     {       "uuid": "63f910f4-e7db-11ea-badf-d039ea14ccfe",       "name": "VG_ARCHIVE2",       "_links": {         "self": {           "href": "/api/storage/volumes/63f910f4-e7db-11ea-badf-d039ea14ccfe"         }       }     }   ],   "num_records": 1,   "_links": {     "self": {       "href": "/api/storage/volumes?name=VG*"     }   } Am I missing something? ... View more

Hi all,   Can someone confirm that the 'LastTransferDuration' from get-ncsnapmirror is in seconds please? Want to ensure I'm dividing by the right number of '60's' ... View more