[Bug]: Systemuser "unset" not working
krausi24 opened this issue · 1 comments
krausi24 commented
Summary
Setting the state to "unset" results in error:
fatal: [dkr_adc4 -> localhost]: FAILED! => {"changed": false, "msg": "value of state must be one of: absent, present, got: unset"}
According documentation it should be possible:
Issue Type
Bug Report
Component Name
netscaler.adc.systemuser
Python Version
Python 3.10.6
Ansible Version
ansible [core 2.14.6]
config file = /etc/ansible/ansible.cfg
configured module search path = ['/home/dkr/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python3/dist-packages/ansible
ansible collection location = /home/dkr/.ansible/collections:/usr/share/ansible/collections
executable location = /usr/bin/ansible
python version = 3.10.6 (main, Mar 10 2023, 10:55:28) [GCC 11.3.0] (/usr/bin/python3)
jinja version = 3.0.3
libyaml = True
Ansible Configuration
$ ansible-config dump --only-changed
netscaler.adc Collection Version
Collection Version
------------- -------
netscaler.adc 2.0.1
Target NetScaler Version
14.1 17.38
Equivalent NetScaler CLI Command
Steps to Reproduce
- name:
tags: SYSTEMUSER_edit
delegate_to: localhost
netscaler.adc.systemuser:
nsip: "{{ ansible_host }}"
nitro_user: "{{ nitro_user }}"
nitro_pass: "{{ nitro_pass }}"
validate_certs: "{{ validate_certs }}"
state: "unset"
username: "{{ item['SYSTEMUSER_username'] }}"
externalauth: "{{ item['SYSTEMUSER_externalauth'] }}"
Expected Results
Unset is working
Actual Results
Additional Notes
No response
sumanth-lingappa commented
@krausi24, the unset
state is added in 2.4.0
However, while reproducing this, I found another issue as below for the systemuser
module
fatal: [localhost]: FAILED! => {"changed": false, "msg": "argument 'timeout' is of type <class 'str'> and we were unable to convert to float: <class 'str'> cannot be converted to a float"}
The task I tried was
- name: Reset the user
delegate_to: localhost
netscaler.adc.systemuser:
state: unset
username: testuser
timeout: "true"
I will keep updating this issue