Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#40116 - [ansible] Modules Library Access Fails
Attached to Project:
Community Packages
Opened by Blake Johnson (postlunch) - Sunday, 27 April 2014, 17:02 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Thursday, 26 June 2014, 09:05 GMT
Opened by Blake Johnson (postlunch) - Sunday, 27 April 2014, 17:02 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Thursday, 26 June 2014, 09:05 GMT
|
DetailsDescription:
When attempting to call modules for the Ansible Module Library the error `ERROR: yum is not a legal parameter in an Ansible Playbook` is returned. The modules appear in the directory /usr/share/ansible, and can be read by the current running user. This also occurs with the module path set explicitly via both methods specicified in the [Ansible documentation](http://docs.ansible.com/developing_modules.html). Some chatter regarding the issue online suggests this is not an upstream problem. Additional info: * ansible 1.5.5-1 * 3.14.1-1-ARCH x86_64 Steps to reproduce: Invoke `yum` via a playbook: - name: Install mailutils hosts: mailservers yum: name=mailutils state=latest Receive error during syntax checking: $ ansible-playbook mailservers.yml ERROR: yum is not a legal parameter in an Ansible Playbook |
This task depends upon
Closed by Bartłomiej Piotrowski (Barthalion)
Thursday, 26 June 2014, 09:05 GMT
Reason for closing: No response
Thursday, 26 June 2014, 09:05 GMT
Reason for closing: No response
it looks like this is an issue with how you have ordered the playbook.
All of the errors I have seen with people referencing it have something that they were missing in the playbook.
Is this a new issue with the newest version of ansible and it worked with older version?