You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run a playbook that I tested and works on ONTAP 9.6+ arrays I wanted to use the same for an older array that cannot be updated beyond ONTAP 9.1. Although the first task that I run is this one:
The na_ontap_rest_info module is specifically designed for REST (hence the name), so falling back to ZAPI would be unexpected behavior. You want to use the na_ontap_info module instead, which is implemented with ZAPI.
I was confused because I still saw that na_ontap_info was there and na_ontap_rest_info clearly indicates in its name (as you pointed) that is a REST module.
I would suggest an update in the documentation, either to remove that flag from that module (na_ontap_rest_info) or update the description pointing this out with a link to na_ontap_info for ZAPI. It could prevent some confusion (myself as a good first hand example).
Thanks
Edit: attached screenshot of use_rest under na_ontap_rest_info module
Summary
When I run a playbook that I tested and works on ONTAP 9.6+ arrays I wanted to use the same for an older array that cannot be updated beyond ONTAP 9.1. Although the first task that I run is this one:
Even though the use_rest has the default value (auto) I get a failure when running it against the ONTAP 9.1 array:
This seems that it doesn't fallback or tries ZAPI in this case when it should.
Component Name
na_ontap_rest_info
Ansible Version
ONTAP Collection Version
ONTAP Version
Playbook
Steps to Reproduce
Run the task against a Netapp array running ONTAP 9.1 (any ONTAP <9.6) and watch the task fail instead of falling back to ZAPI.
Expected Results
I expect na_ontap_rest_info detect it's talking to an array that is not REST compatible and needs to switch to ZAPI.
Actual Results
The text was updated successfully, but these errors were encountered: