increasing the time out does not fix the issue. Checking the API on the cluster shows the cluster create completed in around 3 minutes, well below the timeout value set. The hardware is an AFF30
<localhost> ESTABLISH LOCAL CONNECTION FOR USER: 1000
<localhost> EXEC /bin/sh -c 'echo ~1000 && sleep 0'
<localhost> EXEC /bin/sh -c '( umask 77 && mkdir -p "echo /runner/.ansible/tmp"&& mkdir "echo /runner/.ansible/tmp/ansible-tmp-1743594680.267461-114-244816697920844" && echo ansible-tmp-1743594680.267461-114-244816697920844="echo /runner/.ansible/tmp/ansible-tmp-1743594680.267461-114-244816697920844" ) && sleep 0'
Using module file /runner/requirements_collections/ansible_collections/netapp/ontap/plugins/modules/na_ontap_cluster.py
<localhost> PUT /runner/.ansible/tmp/ansible-local-168uuu1n0_/tmpjb3p90mn TO /runner/.ansible/tmp/ansible-tmp-1743594680.267461-114-244816697920844/AnsiballZ_na_ontap_cluster.py
<localhost> EXEC /bin/sh -c 'chmod u+x /runner/.ansible/tmp/ansible-tmp-1743594680.267461-114-244816697920844/ /runner/.ansible/tmp/ansible-tmp-1743594680.267461-114-244816697920844/AnsiballZ_na_ontap_cluster.py && sleep 0'
<localhost> EXEC /bin/sh -c '/usr/bin/python3.11 /runner/.ansible/tmp/ansible-tmp-1743594680.267461-114-244816697920844/AnsiballZ_na_ontap_cluster.py && sleep 0'
<localhost> EXEC /bin/sh -c 'rm -f -r /runner/.ansible/tmp/ansible-tmp-1743594680.267461-114-244816697920844/ > /dev/null 2>&1 && sleep 0'
character limit