Open eliasp opened 1 year ago
@eliasp are you running this on a FSx System?
@eliasp are you running this on a FSx System?
No, 2x on-premises AFF-A400
@eliasp we are trying to replicate this issue, but so far have not been able to.
In your case the create REST API https://library.netapp.com/ecmdocs/ECMLP2885799/html/index.html#/storage/quota_rule_create Is returning a 5308568. I would reach out to the ONTAP team to ask what would cause that.
Thank you! I've opened a support case now and will get back to you once there are any updates which could further help solving this issue.
Strangely, the issue (for which I opened the support case) regarding the initial error message disappeared and I am now completely unable to reproduce it.
The actual issue reported here (lack of idempotency, "msg": "Error on creating quotas rule: calling: storage/quota/rules: got {'message': 'duplicate entry', 'code': '1', 'target': 'uuid'}."
) is still present.
Summary
When applying a quota rule a 2nd time, an error is returned:
Component Name
netapp.ontap.na_ontap_quotas
Ansible Version
ONTAP Collection Version
ONTAP Version
Playbook
Steps to Reproduce
Save the following playbook (e.g.
test-quota.yml
):Apply it for the 1st time:
The quota seems to be created as desired, but the output contains this warning:
As I first believed, this could be connected to the issue, I followed the instructions and manually disabled/enabled the quota for the volume, but it didn't change the actual outcome.
Apply the playbook for the 2nd time:
The result is:
Expected Results
I expect the Ansible playbook to show a proper idempotent behavior:
Actual Results