[TriPython] Ansible Issue

[Chris Rossi]

Have you made sure the docs correspond to the version you're using?
Usually if I try a documented feature and it doesn't work, it means it's
time for me to upgrade.

Chris


On Mon, Mar 13, 2017 at 2:33 PM, Calloway, Chris <cbc at unc.edu> wrote:

> There are a lot of places I could ask this. But I’m going to try here
> first because I know of so many people using Ansible here.
>
> I have a playbook with, among others, this task:
>
>   - name: update all
>     yum:
>     args:
>       name: '*'
>       state: latest
>       skip_broken: yes
>
> Running it with ansible-playbook results in this error for that task:
>
> FAILED! => {"changed": false, "failed": true, "msg": "unsupported
> parameter for module: skip_broken"}
>
> But the skip_broken option is documented for the yum module:
>
> http://docs.ansible.com/ansible/yum_module.html
>
> Is this yet another module where I’m going to be better off having a shell
> task?
>
> --
> Sincerely,
>
> Chris Calloway
> Applications Analyst
> University of North Carolina
> Renaissance Computing Institute
> (919) 599-3530
>
>
> _______________________________________________
> TriZPUG mailing list
> TriZPUG at python.org
> https://mail.python.org/mailman/listinfo/trizpug
> http://tripython.org is the Triangle Python Users Group
-------------- next part --------------
   Have you made sure the docs correspond to the version you're using?**
   Usually if I try a documented feature and it doesn't work, it means it's
   time for me to upgrade.
   Chris
   On Mon, Mar 13, 2017 at 2:33 PM, Calloway, Chris <[1]cbc at unc.edu> wrote:

     There are a lot of places I could ask this. But I***m going to try here
     first because I know of so many people using Ansible here.

     I have a playbook with, among others, this task:

     ** - name: update all
     ** ** yum:
     ** ** args:
     ** ** ** name: '*'
     ** ** ** state: latest
     ** ** ** skip_broken: yes

     Running it with ansible-playbook results in this error for that task:

     FAILED! => {"changed": false, "failed": true, "msg": "unsupported
     parameter for module: skip_broken"}

     But the skip_broken option is documented for the yum module:

     [2]http://docs.ansible.com/ansible/yum_module.html

     Is this yet another module where I***m going to be better off having a
     shell task?

     --
     Sincerely,

     Chris Calloway
     Applications Analyst
     University of North Carolina
     Renaissance Computing Institute
     [3](919) 599-3530

     _______________________________________________
     TriZPUG mailing list
     [4]TriZPUG at python.org
     [5]https://mail.python.org/mailman/listinfo/trizpug
     [6]http://tripython.org is the Triangle Python Users Group

References

   Visible links
   1. mailto:cbc at unc.edu
   2. http://docs.ansible.com/ansible/yum_module.html
   3. file:///tmp/tel:%28919%29%20599-3530
   4. mailto:TriZPUG at python.org
   5. https://mail.python.org/mailman/listinfo/trizpug
   6. http://tripython.org/