We have a quote a few NAS SVMs running accross 2 cDot Clusters that run Ontap 9.4P3, when attempting to use quota-set-entry through the API we receieve following error but only on a handful of SVMs.
"Missing Input: policy"
The strange thing is that it always fails on 4 out 20 SVMs when the policy is not set in the API call, explictly setting the policy in the API calls works fine. I'm interested to know why the behaviour is different between SVMs though, we suspect a configuration difference between SVMs as the ones which fail were setup at a different time from the ones which work. So far we have not been able to find differences between the SVMs which are at fault.
Doing a quota-set-entry call with this data: <quota-set-entry><disk-limit>2097152</disk-limit><file-limit>40960</file-limit><qtree></qtree><quota-target>/vol/volume3_01/qtree298</quota-target><quota-type>tree</quota-type><volume>volume3_01</volume></quota-set-entry>
on DC1_SVM01 fails the the error "Missing Input: policy"
However on DC1_SVM02 (and the other SVM on this cluster) a very similar call succeeds.