Unsupported parameters for (ansible.legacy.command) module: warn
nicobo opened this issue · 1 comments
nicobo commented
Version Information
$>ansible --version
ansible [core 2.14.0]
config file = /home/someuser/someproject/ansible.cfg
configured module search path = ['/home/someuser/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/lib/python3.10/dist-packages/ansible
ansible collection location = /home/someuser/.ansible/collections:/usr/share/ansible/collections
executable location = /usr/local/bin/ansible
python version = 3.10.6 (main, Nov 2 2022, 18:53:38) [GCC 11.3.0] (/usr/bin/python3)
jinja version = 3.1.2
libyaml = True
Role: haxorof.docker_ce, 3.8.0
Steps to Reproduce
- Configure and run the role haproxy.docker_ce
- It fails because
warn
seems now to be unsupported by thecommand
(andshell
) ansible modules : https://stackoverflow.com/questions/74544930/ansible-unsupported-parameters-for-ansible-legacy-command-module-warn
Expected Behavior
It should run.
Actual Behavior
TASK [haxorof.docker_ce : Update repository cache] *********************************************************************************************************************************************************
task path: /home/someuser/.ansible/roles/haxorof.docker_ce/tasks/setup-repository.yml:5
Using module file /usr/local/lib/python3.10/dist-packages/ansible/modules/command.py
[...]
fatal: [somehost]: FAILED! => {
"attempts": 3,
"changed": false,
"invocation": {
"module_args": {
"_raw_params": "apt-get update",
"_uses_shell": true,
"argv": null,
"chdir": null,
"creates": null,
"executable": null,
"removes": null,
"stdin": null,
"stdin_add_newline": true,
"strip_empty_ends": true,
"warn": false
}
},
"msg": "Unsupported parameters for (ansible.legacy.command) module: warn. Supported parameters include: strip_empty_ends, _raw_params, removes, chdir, _uses_shell, stdin, creates, argv, stdin_add_newline, executable."
}
References
No declared issue that I could find.
haxorof commented
Thanks for reporting this plan is to migrate to use FQCN and I believe that will resolve this issue. I am going to run regression tests this weekend before publishing a new release.