same here! in my case I tested on Mac OSX El Capitan. summary: I had
ansible 2.0.0.2 installed, I installed ansible==1.9.2 and 2.0.0.2 was
automatically uninstalled. now it is working fine.
details:
Eduardo-mac:site-packages eduardocerqueira$ sudo pip install ansible==1.9.2
Password:
The directory '/Users/eduardocerqueira/Library/Caches/pip/http' or its
parent directory is not owned by the current user and the cache has been
disabled. Please check the permissions and owner of that directory. If
executing pip with sudo, you may want sudo's -H flag.
The directory '/Users/eduardocerqueira/Library/Caches/pip' or its parent
directory is not owned by the current user and caching wheels has been
disabled. check the permissions and owner of that directory. If executing
pip with sudo, you may want sudo's -H flag.
Collecting ansible==1.9.2
Requirement already satisfied (use --upgrade to upgrade): paramiko in
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages
(from ansible==1.9.2)
Requirement already satisfied (use --upgrade to upgrade): setuptools in
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages
(from ansible==1.9.2)
Requirement already satisfied (use --upgrade to upgrade): PyYAML in
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages
(from ansible==1.9.2)
Requirement already satisfied (use --upgrade to upgrade): pycrypto>=2.6 in
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages
(from ansible==1.9.2)
Requirement already satisfied (use --upgrade to upgrade): jinja2 in
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages
(from ansible==1.9.2)
Requirement already satisfied (use --upgrade to upgrade): ecdsa>=0.11 in
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages
(from paramiko->ansible==1.9.2)
Requirement already satisfied (use --upgrade to upgrade): MarkupSafe in
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages
(from jinja2->ansible==1.9.2)
Installing collected packages: ansible
Found existing installation: ansible 2.0.0.2
Uninstalling ansible-2.0.0.2:
Successfully uninstalled ansible-2.0.0.2
Successfully installed ansible-1.9.2
Eduardo-mac:site-packages eduardocerqueira$ ls -laht |grep ansible
drwxr-xr-x 22 root admin 748B Jan 29 12:21 ansible
drwxr-xr-x 9 root admin 306B Jan 29 12:21
ansible-1.9.2.dist-info
Eduardo-mac:site-packages eduardocerqueira$ ansible --version
ansible 1.9.2
configured module search path = None
On Monday, August 31, 2015 at 10:38:48 AM UTC-4, Dan Swartz wrote:
>
> *How I got here*:
> I have been wanting to prepare for the upgrade to v2.0 for awhile now and,
> having just seen the alpha release, I thought I'd try it... super bad idea,
> it turns out. My whole environment is messed up. I had already apt-gotten
> it, but after this, I apt-removed it, deleted all leftover files, then
> reinstalled it.
>
> *My Current State*:
> I reinstalled everything, unfortunately, my environment is still messed.
> I'm experiencing the following:
>
> $ ansible --version
> Traceback (most recent call last):
> File "/usr/bin/ansible", line 36, in <module>
> from ansible.runner import Runner
> ImportError: No module named runner
> $ env | grep -i ansible
> $
>
>
> *What I need to know*: What commands/actions do I need to do to get my
> environment in a sane state again? I can tell you that my modules, etc, are
> in /usr/share/pyshared/ansible... should that be my ANSIBLE_LIBRARY? Any
> help would be greatly appreciated!
>
> *Some info*:
>
> # uname -a
> Linux HOSTNAME 3.16.0-40-generic #54~14.04.1-Ubuntu SMP Wed Jun 10
> 17:30:45 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
> (Kubuntu)
>
>
--
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/b3ab8ee3-fa57-40c1-8030-bf3e8902f32c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
