Same issue here, but I did some experimenting to see what the problem is. I
found that running the following command:
python -c "import shade"
provided a lot of useful information about why it wasn't loading the shade
library.
~Rich
On Friday, September 23, 2016 at 11:24:41 PM UTC-4, Amit Chaudhary wrote:
>
> I am having the same issue, where it gives error regarding shade. I have
> tried running in virtalenv also but no luck.
>
> On Thursday, August 13, 2015 at 3:26:32 PM UTC-4, David Shrewsbury wrote:
>>
>> The problem is your environment. I use Python from Homebrew, but I don't
>> use a virtualenv b/c it's hard to make ansible play nicely with that.
>>
>> When ansible connects to the host, 'jump' for you, it's going to
>> automatically
>> use the system python. You can set a different interpreter by adding this
>> to
>> your ansible hosts file for the 'jump' host:
>>
>> jump ansible_python_interpreter=/path/to/python
>>
>> The path should point to the interpreter that has shade installed.
>>
>> Alternatively, install shade in the system python.
>>
>> -Dave
>>
>>
>>
>> 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/0b674053-a5ed-4b2c-9413-b06973965044%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
