ansible-collections / netapp.ontap

Ansible collection to support NetApp ONTAP configuration.
https://galaxy.ansible.com/netapp/ontap
GNU General Public License v3.0
51 stars 34 forks source link

na_ontap_nfs falling back to ZAPI, unsupported option tcp_max_xfer_size #131

Closed Timofeyl closed 1 year ago

Timofeyl commented 1 year ago

Summary

  ---------------------------------

Co

Component Name

na_ontap_nfs

Ansible Version

$ ansible --version
[DEPRECATION WARNING]: Ansible will require Python 3.8 or newer on the controller starting with Ansible 2.12. Current version: 3.6.8 (default, Apr  2 2020, 13:34:55) [GCC 4.8.5 
20150623 (Red Hat 4.8.5-39)]. This feature will be removed from ansible-core in version 2.12. Deprecation warnings can be disabled by setting deprecation_warnings=False in 
ansible.cfg.
/home/timofeyl/.local/lib/python3.6/site-packages/ansible/parsing/vault/__init__.py:44: CryptographyDeprecationWarning: Python 3.6 is no longer supported by the Python core team. Therefore, support for it is deprecated in cryptography and will be removed in a future release.
  from cryptography.exceptions import InvalidSignature
ansible [core 2.11.12] 
  config file = /home/user/netapp-ansible/ansible.cfg
  configured module search path = ['/home/user/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/user/.local/lib/python3.6/site-packages/ansible
  ansible collection location = /home/user/.ansible/collections:/usr/share/ansible/collections
  executable location = /home/user/.local/bin/ansible
  python version = 3.6.8 (default, Apr  2 2020, 13:34:55) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)]
  jinja version = 3.0.3
  libyaml = True

ONTAP Collection Version

$ ansible-galaxy collection list
[DEPRECATION WARNING]: Ansible will require Python 3.8 or newer on the controller starting with Ansible 2.12. Current version: 3.6.8 (default, Apr  2 2020, 13:34:55) [GCC 4.8.5 
20150623 (Red Hat 4.8.5-39)]. This feature will be removed from ansible-core in version 2.12. Deprecation warnings can be disabled by setting deprecation_warnings=False in 
ansible.cfg.
/home/timofeyl/.local/lib/python3.6/site-packages/ansible/parsing/vault/__init__.py:44: CryptographyDeprecationWarning: Python 3.6 is no longer supported by the Python core team. Therefore, support for it is deprecated in cryptography and will be removed in a future release.
  from cryptography.exceptions import InvalidSignature
[DEPRECATION WARNING]: [defaults]callback_whitelist option, normalizing names to new standard, use callbacks_enabled instead. This feature will be removed from ansible-core in 
version 2.15. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.

# /home/timofeyl/.local/lib/python3.6/site-packages/ansible_collections
Collection                    Version
----------------------------- -------
amazon.aws                    1.5.1  
ansible.netcommon             2.5.0  
ansible.posix                 1.3.0  
ansible.utils                 2.4.3  
ansible.windows               1.8.0  
arista.eos                    2.2.0  
awx.awx                       19.4.0 
azure.azcollection            1.10.0 
check_point.mgmt              2.2.0  
chocolatey.chocolatey         1.1.0  
cisco.aci                     2.1.0  
cisco.asa                     2.1.0  
cisco.intersight              1.0.18 
cisco.ios                     2.6.0  
cisco.iosxr                   2.6.0  
cisco.meraki                  2.5.0  
cisco.mso                     1.2.0  
cisco.nso                     1.0.3  
cisco.nxos                    2.8.2  
cisco.ucs                     1.6.0  
cloudscale_ch.cloud           2.2.0  
community.aws                 1.5.0  
community.azure               1.1.0  
community.crypto              1.9.8  
community.digitalocean        1.13.0 
community.docker              1.10.2 
community.fortios             1.0.0  
community.general             3.8.3  
community.google              1.0.0  
community.grafana             1.3.0  
community.hashi_vault         1.5.0  
community.hrobot              1.2.1  
community.kubernetes          1.2.1  
community.kubevirt            1.0.0  
community.libvirt             1.0.2  
community.mongodb             1.3.2  
community.mysql               2.3.2  
community.network             3.0.0  
community.okd                 1.1.2  
community.postgresql          1.6.0  
community.proxysql            1.3.0  
community.rabbitmq            1.1.0  
community.routeros            1.2.0  
community.skydive             1.0.0  
community.sops                1.2.0  
community.vmware              1.17.0 
community.windows             1.8.0  
community.zabbix              1.5.1  
containers.podman             1.9.0  
cyberark.conjur               1.1.0  
cyberark.pas                  1.0.13 
dellemc.enterprise_sonic      1.1.0  
dellemc.openmanage            3.6.0  
dellemc.os10                  1.1.1  
dellemc.os6                   1.0.7  
dellemc.os9                   1.0.4  
f5networks.f5_modules         1.13.0 
fortinet.fortimanager         2.1.4  
fortinet.fortios              2.1.3  
frr.frr                       1.0.3  
gluster.gluster               1.0.2  
google.cloud                  1.0.2  
hetzner.hcloud                1.6.0  
hpe.nimble                    1.1.4  
ibm.qradar                    1.0.3  
infinidat.infinibox           1.3.0  
inspur.sm                     1.3.0  
junipernetworks.junos         2.8.0  
kubernetes.core               1.2.1  
mellanox.onyx                 1.0.0  
netapp.aws                    21.7.0 
netapp.azure                  21.10.0
netapp.cloudmanager           21.12.1
netapp.elementsw              21.7.0 
netapp.um_info                21.8.0 
netapp_eseries.santricity     1.2.13 
netbox.netbox                 3.4.0  
ngine_io.cloudstack           2.2.2  
ngine_io.exoscale             1.0.0  
ngine_io.vultr                1.1.0  
openstack.cloud               1.5.3  
openvswitch.openvswitch       2.1.0  
ovirt.ovirt                   1.6.6  
purestorage.flasharray        1.11.0 
purestorage.flashblade        1.8.1  
sensu.sensu_go                1.12.0 
servicenow.servicenow         1.0.6  
splunk.es                     1.0.2  
t_systems_mms.icinga_director 1.26.0 
theforeman.foreman            2.2.0  
vyos.vyos                     2.6.0  
wti.remote                    1.0.3

Collection included to GIT project.

ONTAP Version

::> version
NetApp Release 9.9.1P9: Wed Apr 20 00:42:19 UTC 2022

Playbook

name: "NFS settings"
  na_ontap_nfs:
      state: present
      vserver: "{{ inventory_hostname }}-svm01"
      nfsv3: enabled
      nfsv4: enabled
      nfsv41: disabled
      tcp: enabled
      tcp_max_xfer_size: 1048576
      nfsv4_id_domain: "{{ domain_name }}"
      vstorage_state: enabled
      username: "{{ username }}"
      password: "{{ password }}"
      hostname: "{{ inventory_hostname }}"
      https: true
      validate_certs: false
      use_rest: "auto"

Steps to Reproduce

Expected Results

Expected ok: nfs v4.0 - enabled vstorage - enabled tcp-max-xfer-size 1048576

Instead of real life values (not updated) : ok: nfs v4.0 - disabled vstorage - disabled tcp-max-xfer-size 65536

Actual Results

TASK [services : NFS settings] *****************************************************************************************************************************************************
[WARNING]: Falling back to ZAPI because of unsupported option(s) or option value(s) in REST: ['tcp_max_xfer_size']
ok: [.....]
==============
After that massage some AFF220 storages with Ontap version >9.9.1  don't apply these settings. No any errors, just this warning.
Ontap Version 9.8 works well.

This playbook relates to Day0 configuration only. Restarting this playbook one more time helps.
carchi8py commented 1 year ago

I don't see netapp.ontap in your collection list so you might be using the old version that come with ansible and might not have all the latest bug fixes.

Could you try installing the latest collection and rerunning the playbook and let me know if you get the same error.

ansible-galaxy collection install netapp.ontap

I know we had a bug fix for a similar issue a few months ago (https://github.com/ansible-collections/netapp.ontap#bug-fixes-11) but can't tell if ansible 2.11.12 contain that bug fix or not

carchi8py commented 1 year ago

@Timofeyl i haven't head back from you on this, if this is still an issue after doing the steps above please reopen this issue.