#Error patching SnapMirror

1 messages · Page 1 of 1 (latest)

next mica
#

Hello guys, recently I've upgraded to ontap modules version 22.14.0 and it looks like the the module na_ontap_snapmirror is handling breaking of snapmirror relationship differently than previous versions. I'm getting this warning when I want to delete snapmirror relationship with policy type vault.

[WARNING]: Ignored error(s): Error patching SnapMirror: {'state':
'broken_off'}: calling: snapmirror/relationships/d57b0dba-
fb37-11ef-b841-d039ea4df114: got {'message': 'Transition to broken_off state
failed. Reason:"snapmirror break" is not allowed on destination
"svm0067:svm0067_atlas_vault" which is the destination of a
relationship that has a policy of type "vault" associated with it.\n', 'code':
'13303808'}.

In my eyes it doesn't makes a sense much because when I break the same SM relationship in the CLI, ONTAP is not complaining about anything. Below is the syntax of my playbook.

    - name: "DELETE snapmirror relationships"
      na_ontap_snapmirror:
        state: absent 
        source_endpoint:
           cluster: "{{ cluster }}"
           path: "{{ relation_detail.json.source.path }}"
        destination_endpoint: 
           cluster: "{{ cluster }}"
           path: "{{ relation_detail.json.destination.path }}"
        relationship_state: broken
        source_hostname: "{{ cluster }}"
        https: yes
        validate_certs: no
        hostname: "{{ cluster }}"
        cert_filepath: "{{ cert }}"
        key_filepath: "{{ key }}"

The issue is that although SM relationship is deleted the destination volume remain as a type DP instead of switching to RW. Then I have to manually call from CLI snapmirror break -destination-path svm0067:svm0067_atlas_vault to get it to the RW although there is no relationship anymore. Some ideas here, how to resolve it except explicit breaking SM relationship prior to deletion?

burnt sinew
#

@next mica This is expected behaviour when using a Snapmirror policy of type 'vault'.
Vault relationship is for backup or retention, so operations like relationship type 'broken' and conversion of volume type from DP to RW are not allowed. As you mentioned after deleting the Snapmirror, you must manually change the volume type from dp to rw when using vault type. For breaking the snapmirror and promote the destination to writable please use other policy types instead.