Could you resolve the issue? If yes, please share the solution here. I am not using virtualenv, still getting the same issue.
Thank you On Thursday, July 21, 2016 at 10:24:50 PM UTC+2, [email protected] wrote: > > Hi, forgive me for my bad english. > > I have exactly the same problem with ansible 2.2 and python 2.7. All > packages are installed in system, no venv but ansible continue with > fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": > "shade is required for this module"} > > I know this post is already solved since 2015, but if someone could help > me ... > > Thanks. > > Le vendredi 14 août 2015 21:36:11 UTC+2, Guido García a écrit : >> >> Thanks James. Now it works like a charm. >> >> El viernes, 14 de agosto de 2015, 19:12:16 (UTC+2), James Martin escribió: >>> >>> If you've installed shade into a virtualenv on your ansible control >>> machine, you may need to tell ansible to use that virtualenv in order to >>> detect it. I've done it like so in my hosts file for other modules (like >>> boto): >>> >>> localhost ansible_python_interpreter="/usr/bin/env python" >>> >>> - James >>> >>> On Wednesday, July 29, 2015 at 3:26:48 PM UTC-4, Chris Gordon wrote: >>>> >>>> I'm trying to use the os_server module in Ansible 2.0 and get the >>>> following error: >>>> >>>> fatal: [jump]: FAILED! => {"changed": false, "failed": true, "msg": >>>> "shade is required for this module"} >>>> >>>> Here's what I have: >>>> >>>> - Python 2.7.10 (Mac, installed via Homebrew) >>>> - Using a virtual environment. >>>> - shade installed in venv via pip (pulled all of it's dependencies, at >>>> least as far as I can tell) >>>> - Ansible cloned from git, devel branch at >>>> commit 8798ce1973a5fd0f8d84e001281699337ddabda4 >>>> - Installed ansible 2.0 by "python setup.py install" from the venv >>>> python interpreter. It installed in site-packages as expected. >>>> >>>> With python in the venv, I can import shade without a problem and >>>> create some shade objects. >>>> >>>> I'm just starting to test with 2.0, so I have a very simply playbook >>>> calling just a single role with a single task. My Openstack.rc file is >>>> sourced and present in my environment. Other openstack cli tools (nova, >>>> neutron, etc.) work fine, so I don't include an auth dictionary in the >>>> task. >>>> >>>> Playbook: >>>> >>>> - hosts: jump >>>> connection: local >>>> roles: >>>> - create_vm >>>> >>>> >>>> create_vm role's task: >>>> >>>> - os_server: >>>> state: present >>>> name: jump >>>> image: centos7u1-cloud >>>> flavor: ostck.t2.v3.small >>>> key_name: mykeyname >>>> nics: >>>> - net-name: priv_net >>>> meta: >>>> group: jump >>>> >>>> >>>> >>>> Any ideas? Happy to provide more details or test anything. >>>> >>>> Thanks, >>>> Chris >>>> >>> -- 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/75b58ce4-8d2a-4adb-8c77-d61406003f0e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
