Arch Linux

ntnllarch

Member

Registered: 2014-05-08

Posts: 8

Ansible 2.6 package / binary version mismatching

Hello everybody,

I just performed a pacman -Syu that has upgraded my ansible installation to ansible-2.6.0-1.
I need the 2.6 for some new Boto modules for interface AWS SDK.

After the installation I'm still getting error using the new ec2_eip_facts module. Actually, the ansible binary shows still the version 2.5:

[antonello@LinuxArch playbooks]$ ansible --version
ansible 2.5.5
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/home/antonello/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.15 (default, May  1 2018, 20:16:04) [GCC 7.3.1 20180406]
[antonello@LinuxArch playbooks]$ pacman -Q ansible
ansible 2.6.0-1

I'm trying to understand whether I am wrong, expecting the 2.6.0-1 binary version, or that is a packaging bug/issue. I made some research in internet, without luck. Can anybody please advice?

Many thanks,

Last edited by ntnllarch (2018-07-04 08:35:24)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,209

Re: Ansible 2.6 package / binary version mismatching

Whatever ansible you are calling there it isn't the ansible from the repos. Did you ever install it using pip? Did you get warnings about existing files that you decided to force over without telling anyone?

ntnllarch

Member

Registered: 2014-05-08

Posts: 8

Re: Ansible 2.6 package / binary version mismatching

Whatever ansible you are calling there it isn't the ansible from the repos. Did you ever install it using pip? Did you get warnings about existing files that you decided to force over without telling anyone?

thanks a lot V1del, you are right, I installed in the past ansible 2.5 via pip, so I understand they were conflicting in some way. Not sure to understand which one I should prefer, and how Arch handle the double installation.
Actually now, after removing both, and reinstalling just the ansible 2.6 from the repository using pacman, I get an error executing ansible:

[antonello@LinuxArch temp]$ /usr/bin/ansible
Traceback (most recent call last):
  File "/usr/bin/ansible", line 40, in <module>
    from ansible.errors import AnsibleError, AnsibleOptionsError, AnsibleParserError
ImportError: No module named ansible.errors

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,209

Re: Ansible 2.6 package / binary version mismatching

For system wide installations it is usually more recommended to use the pacman packages if avaialable. If you must use pip use --user local installation or venvs

The remaining error still points to something regarding your python setup not being as it should be you might want to strace that invocation to find out which library path is trying to be resolved.

Last edited by V1del (2018-07-04 09:38:48)

ntnllarch

Member

Registered: 2014-05-08

Posts: 8

Re: Ansible 2.6 package / binary version mismatching

For system wide installations it is usually more recommended to use the pacman packages if avaialable. If you must use pip use --user local installation or venvs

The remaining error still points to something regarding your python setup not being as it should be you might want to strace that invocation to find out which library path is trying to be resolved.

Thanks so much V1del, I definitely fixed upgrading both to 2.6, many thanks for your help!

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,209

Re: Ansible 2.6 package / binary version mismatching

Do you now have both ansible from the repos as well as a pip install? that's almost guaranteed to run into issues, seriously don't use both at the same time.

However if it is [SOLVED] please mark the topic as such by editing the title.