Closed AwesomeNameMan closed 2 years ago
This is an issue related to REST support in this module. The issue is fixed in 21.18.0 but I would suggest to wait until 21.18.1 is released (today) as it addresses a few issues as highlighted at: https://github.com/ansible-collections/netapp.ontap
closing this as 21.18.1 was released on Galaxy https://galaxy.ansible.com/netapp/ontap
Summary
When creating a vserver peer relationship on 2 clusters, the relationship is not automatically accepted after creation. This worked in a older version of the na_ontap_vserver_peer module. It seems that the culprit could be the new peer_options. When using the deprecated parameters for the destination cluster in an older version, all worked fine.
Component Name
na_ontap_vserver_peer
Ansible Version
ONTAP Collection Version
ONTAP Version
Playbook
Steps to Reproduce
Expected Results
After creating the vserver peer relationship the destination cluster should accept the incoming request from the source cluster and accept the vserver peer handshake.
Actual Results