Description of problem: When the "package" module is provided a binary path instead of a package name task fails with "No group X available" error. Version-Release number of selected component (if applicable): ansible-2.7.10-1.fc29.noarch python3-libdnf-0.28.0-1.fc29.x86_64 python3-dnf-4.2.1-1.fc29.noarch How reproducible: Always. Example playbook: - hosts: localhost tasks: - name: Install packages package: name: - /usr/bin/virtualenv Steps to Reproduce: ansible-playbook packages.yml Actual results: fatal: [localhost]: FAILED! => { "changed": false, "msg": "No group usr/bin/virtualenv available.", "results": []} Expected results: Package python3-virtualenv installed on the system. Additional info: dnf install /usr/bin/virtualenv works as expected
Well, I don't see this as a supported way to call the module in the docs: = name A package name or package specifier with version, like `name-1.0'. When using state=latest, this can be '*' which means run: dnf -y update. You can also pass a url or a local path to a rpm file. To operate on several packages this can accept a comma separated string of packages or a list of packages. (Aliases: pkg) Care to file a RFE upstream?
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
> Care to file a RFE upstream? Ok, filed as https://github.com/ansible/ansible/issues/66424