Snapmirror Error when resync from Broken-Off | NetApp | Page 1

boreal cargo Apr 15, 2024, 5:31 AM

#

We are getting this error (not always) when using the snapmirror module:

"Error patching SnapMirror: {'state': 'snapmirrored'}: job reported error: Timeout error: Process still running, received {'job': {'uuid': 'xxxxx-fae6-11ee-9715-xxxxx', '_links': {'self': {'href': '/api/cluster/jobs/8964c220-fae6-11ee-9715-d039ea369be2'}}}}."

boreal cargo Apr 15, 2024, 5:53 AM

#

Snapmirror Error when resync from Broken-Off

boreal cargo Apr 16, 2024, 7:31 AM

#

https://github.com/ansible-collections/netapp.ontap/issues/208

GitHub

Snapmirror-Resync fails on different Ontap-versions · Issue #208 · ...

Summary When I try to resync a broken-off snapmirror-relationsship between two Ontap-volumes on two different Ontap-clusters running on different Ontap-Versions the task fails. The error message is...

modern talon Apr 18, 2024, 9:33 PM

#

This might be taking longer than the timout, will try to reproduce and get back to you

boreal cargo Apr 24, 2024, 6:22 AM

#

@modern talon Ansible returns an error after approx. 60 seconds. However, the module was given 86400s (= 1 day) as "transferring_time_out".

modern talon Apr 24, 2024, 6:32 PM

#

Are able to resync the relationship in cli successfully?

boreal cargo Apr 25, 2024, 2:13 PM

#

No

modern talon Apr 29, 2024, 6:28 PM

#

snapmirror module is just relaying the same what you try from cli, so module is working as expected when you run from cli.

rose elm May 10, 2024, 6:38 AM

#

Hello,
that the resync fails when starting from CLI is a false infrormation. This is successful. Also the resync started using Ansible is successful, but the Ansible-module is reporting before completion an error.

#Snapmirror Error when resync from Broken-Off