topic Re: Ansible is not able to connect to ONTAP - NetApp API failed in Network and Storage Protocols

Ansible is not able to connect to ONTAP - NetApp API failed

Bhargav — Wed, 04 Jun 2025 09:58:10 GMT

Kindly help how to resolve the issue for automation of ontap with ansible

TASK [Volume Create] ***************************************************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error on vserver: “JPR_NETAPP_A400_1756_01_SVM”: NetApp API failed. Reason - Unexpected error:UnicodeEncodeError('latin-1', '“10.78.198.52”:443', 0, 1, 'ordinal not in range(256)')"}

Re: Ansible is not able to connect to ONTAP - NetApp API failed

aladd — Tue, 09 Aug 2022 04:28:56 GMT

Can you recreate this and collect logging from EMS for the same timeframe so we can see the failure from storage?

::>event log show -time <MM/DD/YYYY HH:MM:SS>..<MM/DD/YYYY HH:MM:SS>

You would just need to fill in the 10 second window to when the test occurred in each section.

Re: Ansible is not able to connect to ONTAP - NetApp API failed

NetApp_SR — Tue, 09 Aug 2022 04:52:27 GMT

Playbooks are sensitive to copy paste that can alter spacing and indentation. Also EOL and tab characters. This could also be related to special characters. {, }, [, ], ,, &, :, *, #, ?, |. -, <. >, =, !, %, @, \. There are online validators for yaml files that may help you identify the issue if EMS does not reveal the issue.