# Ansible 2.15 Warning message

**URL:** <https://forum.ansible.com/t/ansible-2-15-warning-message/38347>\
**Category:** Ansible Project\
**Tags:** galaxy-ng\
**Created:** [August 17, 2023, 3:01pm UTC](https://forum.ansible.com/t/ansible-2-15-warning-message/38347 "2023-08-17T15:01:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dhirender\_Yadav](https://avatars.discourse-cdn.com/v4/letter/d/f14d63/32.png) [@Dhirender\_Yadav](https://forum.ansible.com/u/Dhirender_Yadav)\
**Post date:** [August 17, 2023, 3:01pm UTC](https://forum.ansible.com/t/ansible-2-15-warning-message/38347/1 "2023-08-17T15:01:37Z")

</div>

Hi Team,

Recently we have upgraded to ansible 2.15 and we are getting below WARNINGS.

**Please find the below for the ansible version and collection installed.**

~$ ansible-galaxy collection list -p /home/test/

[DEPRECATION WARNING]: DEFAULT\_GATHER\_SUBSET option, the module\_defaults keyword is a more generic version and can apply to all calls to the M(ansible.builtin.gather\_facts) or M(ansible.builtin.setup) actions, use module\_defaults

instead. This feature will be removed from ansible-core in version 2.18. Deprecation warnings can be disabled by setting deprecation\_warnings=False in ansible.cfg.

# /home/test/ansible\_collections

Collection Version

* * *

ansible.posix 1.5.4

ansible.utils 2.10.3

community.general 4.6.1

:~$

:~$ ansible --version

ansible-playbook [core 2.15.2]

config file = /home/test/ansible.cfg

configured module search path = [‘/home/test/modules’]

ansible python module location = /usr/local/lib/python3.9/site-packages/ansible

ansible collection location = /home/test

executable location = /usr/local/bin/ansible-playbook

python version = 3.9.16 (main, Dec 21 2022, 10:57:18) [GCC 8.5.0 20210514 (Red Hat 8.5.0-17)] (/usr/bin/python3.9)

jinja version = 3.1.2

libyaml = False

**Ansible playbook used for the testing:**

**:~$ cat test.yml**

---

<div class="post-metadata">

**Author:** ![Dhirender\_Yadav](https://avatars.discourse-cdn.com/v4/letter/d/f14d63/32.png) [@Dhirender\_Yadav](https://forum.ansible.com/u/Dhirender_Yadav)\
**Post date:** [September 6, 2023, 3:25am UTC](https://forum.ansible.com/t/ansible-2-15-warning-message/38347/2 "2023-09-06T03:25:27Z")

</div>

Hi Team,

Can someone help with this issue ?

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [September 6, 2023, 5:19am UTC](https://forum.ansible.com/t/ansible-2-15-warning-message/38347/3 "2023-09-06T05:19:12Z")

</div>

Hi,

I think it would help if you would say which specific message do you  
mean. There are a lot of different messages in what you posted.

Cheers,  
Felix

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\
**Post date:** [September 6, 2023, 2:06pm UTC](https://forum.ansible.com/t/ansible-2-15-warning-message/38347/4 "2023-09-06T14:06:02Z")

</div>

The first warning seems like a deprecation, which you should be able  
to check via `ansible-config dump --only-changed`.  
The 2nd warning seems due to a ansible-core vs selective callback  
plugin version mismatch.  
The 3rd is probably also a version incompatibility, but for the  
ansible.netcommon collection. I would open an issue in here  
[https://github.com/ansible-collections/ansible.netcommon/issues](https://github.com/ansible-collections/ansible.netcommon/issues)