# change in reporting in 2.10.1? **URL:** \ **Category:** Ansible Project\ **Created:** [September 29, 2020, 8:37pm UTC](https://forum.ansible.com/t/change-in-reporting-in-2-10-1/33924 "2020-09-29T20:37:16Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Josef\_Fortier](https://avatars.discourse-cdn.com/v4/letter/j/f6c823/32.png) [@Josef\_Fortier](https://forum.ansible.com/u/Josef_Fortier)\ **Post date:** [September 29, 2020, 8:37pm UTC](https://forum.ansible.com/t/change-in-reporting-in-2-10-1/33924/1 "2020-09-29T20:37:16Z")
After updating (pip uninstall, then re-install) and running an adhoc command, say ansible -m ping all I’m seeing many pages of info messages, of the form task 1: [Continuously incrementing list of hosts] ok: HOST ok: HOST ok: HOST eventually followed by the output I’m used to seeing. This seems to be true for playbooks too (they seem to execute fine). Am I missing a new configuration variable ---
**Author:** ![Josef\_Fortier](https://avatars.discourse-cdn.com/v4/letter/j/f6c823/32.png) [@Josef\_Fortier](https://forum.ansible.com/u/Josef_Fortier)\ **Post date:** [October 7, 2020, 3:06pm UTC](https://forum.ansible.com/t/change-in-reporting-in-2-10-1/33924/2 "2020-10-07T15:06:09Z")
Has anyone else seen this? To clarify, an ansible -m ping produces a very large amount of progress notes. Each host generates far greater output A “task 1:” header, with the host and a list of all previous hosts processed. The list starts at one host, and by the end includes all the hosts. This is followed by several “ok: [HOSTNAME]” (with other tasks there’s more detail) By the end, there’s a long list of hosts in the “task 1:” line. Then the end has several repetitions of the v2.9.X expected summary output Also should note that I listed the collection version in the subject, ansible-core is at 2.10.0 I’ve tried modifying ANSIBLE\_STDOUT\_CALLBACK (in the config and as an environmental variable). FWIW the callback names change in 2.10 (longer qualified names). It smells like some new output modifying feature that doesn’t make the transition for my setup, but also seems to have something to do with parallelism. I’ve tried several versions of python, no change. I’ve tried to keep fairly current with ansible installs, but this behavior makes the current version quite unattractive. Functionality seems the same. ---
**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\ **Post date:** [October 7, 2020, 3:11pm UTC](https://forum.ansible.com/t/change-in-reporting-in-2-10-1/33924/3 "2020-10-07T15:11:52Z")
I have not seen this, and I have no idea what could cause this. Your output (although you only gave a snippet which makes it difficult) appears to be from the `default` callback, however when running `ansible` (the adhoc command) we explicitly prevent using the `default` callback. Might help to see the output of `ansible-config dump --only-changed` As well as some pastebin of the full output, including `-vvvv` When run with `-vvvv` you should see a line that starts with: Loading callback plugin ---
**Author:** ![Josef\_Fortier](https://avatars.discourse-cdn.com/v4/letter/j/f6c823/32.png) [@Josef\_Fortier](https://forum.ansible.com/u/Josef_Fortier)\ **Post date:** [October 7, 2020, 5:36pm UTC](https://forum.ansible.com/t/change-in-reporting-in-2-10-1/33924/4 "2020-10-07T17:36:08Z")
Thanks ansible-config dump --only-changed (I’m running a directory based config, clearly) ANSIBLE\_PIPELINING(/home/fortier/src/ansible/ansible.cfg) = True CACHE\_PLUGIN(/home/fortier/src/ansible/ansible.cfg) = jsonfile CACHE\_PLUGIN\_CONNECTION(/home/fortier/src/ansible/ansible.cfg) = .tmp/facts DEFAULT\_CALLBACK\_WHITELIST(/home/fortier/src/ansible/ansible.cfg) = [‘skippy’, ‘unixy’, ‘actionable’, ‘yaml’, ‘debug’, ‘dense’] DEFAULT\_FORKS(/home/fortier/src/ansible/ansible.cfg) = 75 DEFAULT\_HOST\_LIST(/home/fortier/src/ansible/ansible.cfg) = [‘/home/fortier/src/ansible/inventory’] DEFAULT\_LOAD\_CALLBACK\_PLUGINS(/home/fortier/src/ansible/ansible.cfg) = True DEFAULT\_LOG\_PATH(/home/fortier/src/ansible/ansible.cfg) = /home/fortier/src/ansible/.ansible.log DEFAULT\_ROLES\_PATH(/home/fortier/src/ansible/ansible.cfg) = [‘/home/fortier/src/ansible/roles’] DEFAULT\_STDOUT\_CALLBACK(/home/fortier/src/ansible/ansible.cfg) = skippy DEFAULT\_TIMEOUT(/home/fortier/src/ansible/ansible.cfg) = 30 DEFAULT\_VAULT\_PASSWORD\_FILE(/home/fortier/src/ansible/ansible.cfg) = /home/fortier/src/ansible/.ansible\_vault\_password INTERPRETER\_PYTHON(/home/fortier/src/ansible/ansible.cfg) = auto\_silent RETRY\_FILES\_ENABLED(/home/fortier/src/ansible/ansible.cfg) = False I’m a little leary of dumping host names on a public forum Here’s the first screen of output from non-verbose output (edited hosts) Should give a more complete picture 🙂 ---
**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\ **Post date:** [October 7, 2020, 7:54pm UTC](https://forum.ansible.com/t/change-in-reporting-in-2-10-1/33924/5 "2020-10-07T19:54:32Z")
There is a small change in behavior between 2.9 and 2.10. If you are up to testing, take a look at [https://github.com/ansible/ansible/pull/59932](https://github.com/ansible/ansible/pull/59932) I’ve added your reproducer to that PR ---
**Author:** ![Josef\_Fortier](https://avatars.discourse-cdn.com/v4/letter/j/f6c823/32.png) [@Josef\_Fortier](https://forum.ansible.com/u/Josef_Fortier)\ **Post date:** [October 8, 2020, 7:30pm UTC](https://forum.ansible.com/t/change-in-reporting-in-2-10-1/33924/6 "2020-10-08T19:30:03Z")
I’ve never pulled the repo and tried to build/test ansible before. I’d be worried that the time it would take me to set it up might be more then desirable. Would it be useful to do over the weekend? ---
**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\ **Post date:** [October 8, 2020, 7:35pm UTC](https://forum.ansible.com/t/change-in-reporting-in-2-10-1/33924/7 "2020-10-08T19:35:38Z")
In the short term, you can work around the issue, by removing whitelist items for stdout plugins other than the one you have listed for stdout: Related config entries: DEFAULT\_CALLBACK\_WHITELIST(/home/fortier/src/ansible/ansible.cfg) = [‘skippy’, ‘unixy’, ‘actionable’, ‘yaml’, ‘debug’, ‘dense’] DEFAULT\_LOAD\_CALLBACK\_PLUGINS(/home/fortier/src/ansible/ansible.cfg) = True DEFAULT\_STDOUT\_CALLBACK(/home/fortier/src/ansible/ansible.cfg) = skippy The callback whitelist should typically be for any callback that is not a stdout callback. All of them that you have listed in the whitelist are stdout callbacks. Only 1 should ever be loaded, that is where the bug is. Also, if you don’t want to use `skippy` as the stdout callback for adhoc, then change the bin\_ansible\_callback value to False, instead of True.