Issue 62360 not fixed?

Archives Ansible Project
1

I opened issue 62360 and when I looked at it today, I saw it had been closed with the remark This has been fixed in supported versions of Ansible. I upgraded:

ansible [core 2.12.4]
config file = /etc/ansible/ansible.cfg
configured module search path = [‘/home/ubuntu/.ansible/plugins/modules’, ‘/usr/share/ansible/plugins/modules’]
ansible python module location = /usr/local/lib/python3.8/dist-packages/ansible
ansible collection location = /home/ubuntu/.ansible/collections:/usr/share/ansible/collections
executable location = /usr/local/bin/ansible
python version = 3.8.5 (default, Jul 28 2020, 12:59:40) [GCC 9.3.0]
jinja version = 3.0.1
libyaml = True

and appears that the original problem persists. Should I open a new issue?

2

Seems to work as expected for me. state=absent with an asterisk for the name removed all the matching packages.

3

Were packages actually removed? I noted in the original issue that if package are removed, it works. It no packages are removed, it will fail.

Can you try running the playbook again?