Bug #29627
ansible-runner verbosity doesn't show verbose output
Fixed in Releases:
Found in Releases:
Description
Even when increasing the verbosity, Ansible jobs executed doesn't show verbose output.
# hammer settings list | grep ansible_verbosity ansible_verbosity | Default verbosity level | 3
330: TASK [Apply roles] ************************************************************* 331: 332: TASK [ansible-role-motd : Ensure the MOTD file is present and updated] ********* 333: changed: [client.example.com] 334: PLAY RECAP ********************************************************************* 335: client.example.com : ok=3 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 336: Exit status: 0
Associated revisions
History
#1
Updated by The Foreman Bot about 2 years ago
- Assignee set to Nagoor Shaik
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman_ansible/pull/343 added
#2
Updated by Nagoor Shaik about 2 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman_ansible|5a8311443f1a4bff73e20faf6eec456d809eeabd.
Fixes #29627 - fixed ansible-runner verbosity in plays