Closed snkellner closed 2 years ago
Same issue using applications: ["snapmirror"] It seems a regression: this role worked fine till Ontap collection 21.13.1 and it stop working using 21.14.0. or later.
Yes, I would expect the issue to be the same whether the application is snapmirror or flexcache.
We added REST support in 21.14.0 so a possible work-around is to force ZAPI with
use_rest: never
in your task.
We tried to reproduce this with ONTAP systems, without success. So maybe it's FSx specific. Retrieving the job status is a cluster level operation in ONTAP classic. We'll look into this.
I could reproduce the issue. The peering relationship is actually created, but the job is not found. This also prevents to accept the peering request,
We are suspecting an ONTAP bug that is specific to FSx and svm/peers. We'll add a work-around in the vserver_peer module.
ONTAP should have a fix in 9.11.0 release. But we can ignore the error in Ansible.
fixed in 21.18.0
Summary
When I try to create a vserver peer with application flexcache for vservers on two different FSxN instances it fails. The vserver peer remains in state pending and I have to accept the vserver peering on the destination cluster manually.
Component Name
na_ontap_vserver_peer
Ansible Version
ONTAP Collection Version
ONTAP Version
Playbook
Steps to Reproduce
Expected Results
I expect the vserver peering is successful without manual intervention.
Actual Results