Unsupported parameters for (ansible.legacy.command) module: warn

[fnschroeder]

Issue
Consistent error when running the list users preliminary task due to task using unsupported parameter. And any that use the builtin command with warn as a parameter.

Expected Behavior
Control executing without issues

Actual Behavior
rhel8-ami-build.amazon-ebs.rhel8_ami: TASK [rhel-8-lockdown : PRELIM | List users accounts] **************************
rhel8-ami-build.amazon-ebs.rhel8_ami: fatal: [default]: FAILED! => {"changed": false, "msg": "Unsupported parameters for (ansible.legacy.command) module: warn. Supported parameters include: stdin, removes, _uses_shell, strip_empty_ends, argv, executable, stdin_add_newline, chdir, creates, _raw_params."}

Control(s) Affected

RHEL8-CIS/tasks/prelim.yml

Line 7 in 0220ed1

warn: no

RHEL8-CIS/tasks/check_prereqs.yml

Line 10 in 0220ed1

warn: false

RHEL8-CIS/tasks/section_3/cis_3.1.x.yml

Line 69 in 0220ed1

warn: no

Example:
- name: "PRELIM | List users accounts" command: "awk -F: '{print $1}' /etc/passwd" args: warn: false changed_when: false check_mode: false register: users

Environment:

• Ansible Version: 2.14.1
• Using branch: main

Additional Notes
According to:
https://github.com/ansible/ansible/blob/stable-2.14/changelogs/CHANGELOG-v2.14.rst#removed-features-previously-deprecated
command/shell - remove deprecated warn module param

Possible Solution
This might be a quick fix to just remove the warn parameter

[jmighion]

This is also affecting us on ansible 2.14.1, but downgrading to 2.13.7 worked. I did not test the versions in between though.

The commit above looks like it would address the issue.

[uk-bolly]

hi @fnschroeder @jmighion

Thank you for raising this issue, feedback like this helps us to improve.
I am happy to say this is being address in the jan23 release to devel. Hopefully over the next week will be merged.

Regards

uk-bolly

[CFSNM]

Hello!

I saw that the fixes for this issue were merged on January 23rd, but the latest published version (2.1.0) does not contain the fix. Do you have any plan to release a new version including all these fixes?

[uk-bolly]

Hello!

I saw that the fixes for this issue were merged on January 23rd, but the latest published version (2.1.0) does not contain the fix. Do you have any plan to release a new version including all these fixes?

hi @CFSNM

We want to try and get the update out asap. We have had other client priorities that have taken a precendence (you may have seen alot of updated recently across many repos).
I will see if we can get this out in th enext couple of days into a release.

many thanks

uk-bolly

[uk-bolly]

hi @CFSNM @fnschroeder

Thank you for your patience, you will find that there has been a number of big lifts in work recently and these are now resolved in the latest release.
I will close this issue , please feel free to raise anything should you come across it.
Once again thank you for your feedback.

uk-bolly