[TriPython] Ansible Issue
Calloway, Chris
cbc at unc.edu
Tue Mar 14 11:27:29 EDT 2017
Thanks all, David, Barry, and Chris for the great answers including the one staring me in the face. I am indeed not up to 2.3:
$ ansible --version
ansible 2.2.1.0
…
I pip’d the latest from pypi because it wasn’t in conda-forge.
I’m also running it with (Anaconda) Python 3 which is warned to be experimental. Python 3 and ansible, that is. And on OSX (targets are Centos).
I’m just going to yum through a shell task and see if that works. I end up doing that with a lot of ansible modules. I might be better off just making a bash script but I thought I give ansible a whirl.
--
Sincerely,
Chris Calloway
Applications Analyst
University of North Carolina
Renaissance Computing Institute
(919) 599-3530
On 3/14/17, 6:42 AM, "TriZPUG on behalf of David Handy" <trizpug-bounces+cbc=unc.edu at python.org on behalf of david at handysoftware.com> wrote:
I run the "bleeding edge" devel branch of Ansible from here: https://github.com/ansible/ansible
Everything I see in the docs is in the devel version, but I sometimes run into bugs too! Latest pull from a couple of days ago has been pretty good so far. So, if you absolutely want to use a feature you see in the docs *right now*, you have that option.
David H
On Monday, March 13, 2017 10:29pm, "Barry Peddycord III" <isharacomix at trilug.org> said:
> According to the docs,
> skip_broken is "added in 2.3", and 2.3 hasn't been
> release yet! The ansible docs are tracking the development version of
> github, meaning that features will appear in the docs before they go live.
> :)
>
> On Mon, Mar 13, 2017 at 10:12 PM Chris Rossi <chris at archimedeanco.com>
> wrote:
>
> > 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/
> > _______________________________________________
> > TriZPUG mailing list
> > TriZPUG at python.org
> > https://mail.python.org/mailman/listinfo/trizpug
> > http://tripython.org is the Triangle Python Users Group
> According to the docs, skip_broken is "added in 2.3", and 2.3 hasn't been
> release yet! The ansible docs are tracking the development version of
> github, meaning that features will appear in the docs before they go live.
> :)
> On Mon, Mar 13, 2017 at 10:12 PM Chris Rossi
> <[1]chris at archimedeanco.com>
> wrote:
>
> ** **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][2]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][3]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][4](919) 599-3530
>
> ** ** **_______________________________________________
> ** ** **TriZPUG mailing list
> ** ** **[4][5]TriZPUG at python.org
> ** ** **[5][6]https://mail.python.org/mailman/listinfo/trizpug
> ** ** **[6][7]http://tripython.org is the Triangle Python Users Group
>
> References
>
> ** **Visible links
> ** **1. mailto:[8]cbc at unc.edu
> ** **2. [9]http://docs.ansible.com/ansible/yum_module.html
> ** **3. file:///tmp/tel:%28919%29%20599-3530
> ** **4. mailto:[10]TriZPUG at python.org
> ** **5. [11]https://mail.python.org/mailman/listinfo/trizpug
> ** **6. [12]http://tripython.org/
> _______________________________________________
> TriZPUG mailing list
> [13]TriZPUG at python.org
> [14]https://mail.python.org/mailman/listinfo/trizpug
> [15]http://tripython.org is the Triangle Python Users Group
>
> References
>
> Visible links
> 1. mailto:chris at archimedeanco.com
> 2. mailto:cbc at unc.edu
> 3. http://docs.ansible.com/ansible/yum_module.html
> 4. file:///tmp/tel:(919)%20599-3530
> 5. mailto:TriZPUG at python.org
> 6. https://mail.python.org/mailman/listinfo/trizpug
> 7. http://tripython.org/
> 8. mailto:cbc at unc.edu
> 9. http://docs.ansible.com/ansible/yum_module.html
> 10. mailto:TriZPUG at python.org
> 11. https://mail.python.org/mailman/listinfo/trizpug
> 12. http://tripython.org/
> 13. mailto:TriZPUG at python.org
> 14. https://mail.python.org/mailman/listinfo/trizpug
> 15. http://tripython.org/
>
_______________________________________________
TriZPUG mailing list
TriZPUG at python.org
https://mail.python.org/mailman/listinfo/trizpug
http://tripython.org is the Triangle Python Users Group
More information about the TriZPUG
mailing list