Software Development Kit (SDK) and API Discussions

Extra user entry being created while creating a rule for quota using RestAPI

vkarthi2
54 Views

My customer is creating a quota rule for a specific user using RestAPI, but the call is creating another user " " when the command is run. 

Example -

Created volume and quota, no rule created

 

us01cmqa::> vol show QUOTA_TEST_10

Vserver   Volume       Aggregate    State      Type       Size  Available Used%

--------- ------------ ------------ ---------- ---- ---------- ---------- -----

us01cmqavs1 QUOTA_TEST_10 us01cmqat1f03_nvme_aggr1 online RW 100GB 95.00GB   0%

 

us01cmqa::> quota policy rule show -volume QUOTA_TEST_10 -vserver us01cmqavs1

There are no entries matching your query.

 

Executed the API for creating the rule

 

aneeshpa@us01nasadmin3:~ $ curl -X POST -u "user:********" -k -H "accept: application/json" -H "Content-Type: application/json" -d '{"qtree":{"nme":"quota_test_10"},"space":{"hard_limit":"2147483648"},"svm":{"name":"us01cmqavs1"},"type":"user","volume":{"name":"QUOTA_TEST_10"},"users":[{"name":"user1"}]}'

{

  "job": {

    "uuid": "d0fb5f95-ab22-11f0-9b12-00a098c54541",

    "_links": {

      "self": {

        "href": "/api/cluster/jobs/d0fb5f95-ab22-11f0-9b12-00a098c54541"

      }

    }

  }

}

 

With the above API we have created a rule for one user only, but one more extra entry came, wanted to check is there any way to avoid the extra entry

 

us01cmqa::> quota policy rule show -volume QUOTA_TEST_10 -vserver us01cmqavs1

 

Vserver: us01cmqavs1       Policy: default           Volume: QUOTA_TEST_10

 

                                               Soft             Soft

                         User         Disk     Disk   Files    Files

Type   Target    Qtree   Mapping     Limit    Limit   Limit    Limit  Threshold

-----  --------  ------- -------  --------  -------  ------  -------  ---------

user   ""        ""      off             -        -       -        -          -

user   aneeshpa  quota_test_10 off     2GB        -       -        -          -

 

The entry for user - aneeshpa is expected, but customer isn't sure why user "  " is also being created

0 REPLIES 0
Public