Hi Toshio,

ANSIBLE_LIBRARY is unset. 

$ ansible --version
ansible 2.0.0
  config file = /etc/ansible/ansible.cfg
  configured module search path = /usr/share/ansible

With a little investigation, I see the long listing of 
/usr/share/ansible/packaging shows all files with a date of April 2014, 
even though one level up they are all dated 11/23/15. 

A couple days ago, I did an untar, make, make install of the package. 
Today, I attempted to reinstall pip because I was having these issues:
pip install --upgrade 
http://releases.ansible.com/ansible/ansible-2.0.0-0.6.rc1.tar.gz

And just now I did a pip force reinstall:
# pip install --force-reinstall 
http://releases.ansible.com/ansible/ansible-2.0.0-0.6.rc1.tar.gz

The module files are still all the old ones from April 2014. How do I get 
the updated module files? 



On Wednesday, November 25, 2015 at 7:04:33 PM UTC-6, tkuratomi wrote:
>
> From the traceback you showed in your original message, it looks like 
> somehow you have an old version of the yum module being used with the 
> current rc1 for /usr/bin/ansible-playbook.  items = pkgspec.split(',') 
> from the traceback message is no longer present in the yum module. 
> Perhaps there's some old version of ansible present on the machine and 
> its yum module is overriding the one from rc1 or you have the 
> ANSIBLE_LIBRARY environment variable set to some path where an 
> alternative yum module is living. 
>
> -Toshio 
>
> On Wed, Nov 25, 2015 at 4:44 PM, Joanna Delaporte 
> <[email protected] <javascript:>> wrote: 
> > Alright, it worked with that variable you requested. 
> > 
> > I exported the env var (it didn't work just set in the current shell): 
> > export ANSIBLE_SQUASH_ACTIONS="apt,pkgng" 
> > 
> > And ran this play: 
> > - yum: name="{{ item }}" state=present 
> >   with_items: 
> >     - ypbind 
> >     - rpcbind 
> > 
> > The play succeeded with this variable set. 
> > 
> > Thanks! 
> > Joanna 
> > 
> > On Wednesday, November 25, 2015 at 6:10:42 PM UTC-6, Brian Coca wrote: 
> >> 
> >> if you run the test i asked, i can confirm it will be because of 
> >> argument squashing, which is an optimization that will run on yum but 
> >> not on package. 
> >> 
> >> -- 
> >> Brian Coca 
> > 
> > -- 
> > 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 [email protected] <javascript:>. 
> > To post to this group, send email to [email protected] 
> <javascript:>. 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/ansible-project/eb34144b-5b58-4ce2-b8b9-ef02b71d760b%40googlegroups.com.
>  
>
> > 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/a58566b0-b794-4e1c-932a-cec5ba1a6c53%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to