Open christian-naenny opened 6 months ago
Hi,
In your playbook, since you have added "validate_source_path": true, which will check if another relationship exists as svm name for peer can be aliased in the source. In snapmirror resource, it is trying find out the svm peer relationship if there is an alias of the destination svm.
Hence, you are getting the error Error retrieving SVM peer: calling: svm/peers: got HTTPSConnectionPool(host='clustername', port=443): Read timed out. (read timeout=60).
We are still debugging to see if error is appropriate here, meanwhile can you run the same with "validate_source_path": false, so that the source path will not be validated here.
As you can see in my snippet of the playbook, validate_source_path is set to false! That was the first thing I tried but without any luck. The first version of the playbook did not contain the parameter validate_source_path at all, but I got the same error message!
DEVOPS-6839
Summary
I'm trying to break a snapmirror relationship where the primary cluster is not available. The situation is a disaster recovery exercise where we completely isolate the second datacenter (SAN and IP networks). Our DR cluster contains the DR SVMs. From the perspective of the DR cluster, the primary cluster is now completely unavailable. Upon breaking the snapmirror relationship the error Error retrieving SVM peer: calling: svm/peers: got HTTPSConnectionPool(host='clustername', port=443): Read timed out. (read timeout=60). is thrown.
Component Name
na_ontap_snapmirror
Ansible Version
ONTAP Collection Version
ONTAP Version
Playbook
Steps to Reproduce
Expected Results
I simply expected the snapmirror state to end up like this:
Actual Results