https://github.com/ansible/ansible/issues/41263 still issue on version 2.9.1

Archives Ansible Project
1

Running simple shell commands now produces CHANGED instead of SUCCESS.

ansible --version ansible 2.9.1 config file = /etc/ansible/ansible.cfg configured module search path = ['/home/myuser/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python3.7/site-packages/ansible executable location = /usr/bin/ansible python version = 3.7.5 (default, Oct 17 2019, 12:09:47) [GCC 9.2.1 20190827 (Red Hat 9.2.1-1)]

`
ansible db_server -m shell -a “grep innodb_log_file_size /etc/my.cnf” -k
SSH password:
db01.server.com | CHANGED | rc=0 >>
innodb_log_file_size=512M

db02.server.com | CHANGED | rc=0 >>
innodb_log_file_size=512M

`

Same issue posted : https://github.com/ansible/ansible/issues/41263

2

Hi,

Running simple shell commands now produces CHANGED instead of SUCCESS.

"now" has been for quite a while now. And as you can read in
https://github.com/ansible/ansible/issues/41263, this is not a bug, but
the expected behavior. Reporting success instead of changed was a bug.

If you want a `shell` or `command` task to not result in changed,
simply add `changed_when: false` to the task (not to the module
arguments, but at the same level as `shell` or `command`). See
https://docs.ansible.com/ansible/latest/user_guide/playbooks_error_handling.html#overriding-the-changed-result
for details.

Cheers,
Felix

3

thank you for answer ,

is it possible to use changed_when: false on ad-hoc command mode ?