Add protocol to a vserver is not possible any more

[lucid stirrup]

If I create a vserver with ONTAP 9.11.1 and disallow all protocols first, I am not able to add one or more protocols afterwards.

My yml file to create the vserver

- name: create vserver
  delegate_to: localhost
  netapp.ontap.na_ontap_svm:
    hostname: "{{ netapp_hostname }}"
    username: "{{ netapp_username }}"
    password: "{{ netapp_password }}"
    https: true
    validate_certs: "{{ validate_certs }}"
    state: present
    name: "rene5"
    services:
      cifs:
        allowed: false
      nfs:
        allowed: false
      iscsi:
        allowed: false
      fcp:
        allowed: false
      ndmp:
        allowed: false

The strange part here is, that the vervser does not show any protocols. Neither in allowed protocol nor in disallowed protocol.

cluter::> vserver show -vserver rene5 -fields allowed-protocols ,disallowed-protocols
vserver allowed-protocols disallowed-protocols
------- ----------------- --------------------
rene5   -                 -

Now I am not able to add one or more protocols any more

- name: Add CIFS and NFS Protocol
  delegate_to: localhost
  netapp.ontap.na_ontap_svm:
    hostname: "{{ netapp_hostname }}"
    username: "{{ netapp_username }}"
    password: "{{ netapp_password }}"
    https: true
    validate_certs: "{{ validate_certs }}"
    state: present
    name: "rene5"
    services:
      cifs:
        allowed: true
      nfs:
        allowed: true
        enabled: true

The -vvv show the following output

TASK [my-subrole : Add CIFS and NFS Protocol] 
*******************************
ok: [localhost -> localhost] => {
    "changed": false,
    "invocation": {
        "module_args": {
            "admin_state": null,
            "aggr_list": null,
            "allowed_protocols": null,
            "cert_filepath": null,
            "comment": null,
            "feature_flags": null,
            "force_ontap_version": null,
            "from_name": null,
            "hostname": "lnaszhhdc01.sccloudinfra.net",
            "http_port": null,
            "https": true,
            "ignore_rest_unsupported_options": false,
            "ipspace": null,
            "key_filepath": null,
            "language": null,
            "max_volumes": null,
            "name": "rene5",
            "ontapi": null,
            "password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",
            "root_volume": null,
            "root_volume_aggregate": null,
            "root_volume_security_style": null,
            "services": {
                "cifs": {
                    "allowed": true
                },
                "fcp": null,
                "iscsi": null,
                "ndmp": null,
                "nfs": {
                    "allowed": true,
                    "enabled": false
                },
                "nvme": null
            },
            "snapshot_policy": null,
            "state": "present",
            "subtype": null,
            "use_rest": "auto",
            "username": "admin",
            "validate_certs": false,
            "web": null
        }
    }
}

But this is a lie. With putty the vserver show still no protocols.

cluter::> vserver show -vserver rene5 -fields allowed-protocols ,disallowed-protocols
vserver allowed-protocols disallowed-protocols
------- ----------------- --------------------
rene5   -                 -

[broken urchin]

So the -VVV output show us what Ansilble see the your input as before we pass it on to REST. I have a pretty good idea what might be causing this, let me check the code

[broken urchin]

I have DEVOPS-6351 open for this.

I think this is going to be hard issue to fix, but could you add the following tracing lines to your Playbook, so we can trace the api Get calls and their returns.

https://github.com/ansible-collections/netapp.ontap/wiki/Debugging#tracing-zapi-and-rest-api-calls

THis will create a file call /tmp/ontap-apis.log can you send that to me at [e-mail]