Target host syslog logging accidentally tied to runtime verbosity #18569
Labels
affects_2.2
This issue/PR affects Ansible v2.2
bug
This issue/PR relates to a bug.
P2
Priority 2 - Issue Blocks Release
ISSUE TYPE
COMPONENT NAME
Module execution logging on the target host
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
N/A
SUMMARY
Prior to a56c0bc when ansible executed a module on a target host, the invocation of that module was logged to syslog, which was useful for auditing who's doing what to a particular host with Ansible. After that commit, the logging only happens if the execution of ansible was done with verbosity level 3 or above.
STEPS TO REPRODUCE
Execute ansible-playbook with less than verbosity 3, no indication on remote host that anything was done.
EXPECTED RESULTS
I would expect to see things like:
ACTUAL RESULTS
There is no logging of the module execution.
The text was updated successfully, but these errors were encountered: