#Volume resize on large (500TB+) flexgroup causes na_ontap_volume to fail

1 messages · Page 1 of 1 (latest)

real gate
#

We have been having issues in fsx ontap where it fails when we resize the volume to a bigger size. Not all the time but 60-70% of the time.
Ansible script fails with below error :
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error resizing volume my_vol: job reported error: The volume operation was successful but the size of the volume has not finished updating. Wait a few minutes, and then check that the size of the volume is "800TB" using the "volume show -vserver fsx -volume my_vol -fields size" command. For further assistance, contact technical support., received {'job': {'uuid': 'xxxxxxxxxxxxxx', '_links': {'self': {'href': '/api/cluster/jobs/xxxxxxxxxxxxxxx'}}}}."

However Resize does complete but then upon rerun it fails for another volume which needs resize.

We have given enough time_out value ( i feel it does not fail because it reaches timeout value).

However this is same case when we do the resizing operation manually on filer, but is there a way or a fix for this using api or any other option that could be used.

Any help would be much appreciated.
Thanks.

daring otter
#

You could use Ansibles retry mechanic as a workaround. Example code

- name: Resize volume netapp.ontap.na_ontap_volume: state: present size_change_threshold: 0 size_unit: b size: "{{ volume_target_size }}" name: "{{ volume_name }}" vserver: "{{ vserver_name }}" register: result until: - result is not failed delay: 10 #seconds retries: 3

solid panther
#

I think there's a conflict in this module with max_wait_time , wait_for_completion and the API responding with the error message @real gate has shown. I think wait_for_completion is waiting for a response from the API, and in this case, the API responds with "I'm not done yet". wait_for_completion should ignore this and wait until the task is actually done.