Issue 62360 not fixed?

[John Pfuntner]

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?

[Matt Martz]

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

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/b9dd9e93-b3e3-4d2d-95fb-dd8a99d9142cn%40googlegroups.com.

--

Matt Martz
@sivel
sivel.net

[John Pfuntner]

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?