Hi,
I came across the same issue when I try to run cloudformation module in
CentOS in python virtual env. (it used to work some time ago):
(venv)[root@test ansible]# ansible-playbook aws-cf-provision.yml -vv
...
failed: [localhost] => {"failed": true, "parsed": false}
failed=True msg='boto required for this module'
Traceback (most recent call last):
File
"/root/.ansible/tmp/ansible-tmp-1429011194.43-47297413805384/cloudformation",
line 130, in <module>
sys.exit(1)
NameError: name 'sys' is not defined
Setting up "export PYTHONPATH=/root/venv/lib/python2.6/site-packages" or
"localhost ansible_python_interpreter=/root/venv/bin/python" in hosts makes
the original error disappear but the resource doesn't get created ...
Here is the current error:
(venv)[root@test ansible]# ansible-playbook aws-cf-provision.yml -vv
PLAY [localhost]
**************************************************************
TASK: [Create VPC, internet gateway, route tables and security groups]
********
<localhost> REMOTE_MODULE cloudformation template=VPCStack.json
state=present region=eu-west-1 stack_name=VPCStack-dev2
aws_access_key=*******************************
aws_secret_key==*******************************
failed: [localhost] => {"failed": true}
FATAL: all hosts have already failed -- aborting
PLAY RECAP
********************************************************************
to retry, use: --limit @/root/aws-cf-provision.retry
localhost : ok=0 changed=0 unreachable=0 failed=1
(venv)[root@test ansible]# pip list
ansible (1.9.0.1)
argparse (1.3.0)
awscli (1.7.18)
bcdoc (0.13.0)
boto (2.38.0)
botocore (0.101.0)
colorama (0.3.3)
docutils (0.12)
ecdsa (0.13)
httplib2 (0.9)
Jinja2 (2.7.3)
jmespath (0.6.1)
List (1.3.0)
MarkupSafe (0.23)
ordereddict (1.1)
paramiko (1.15.2)
pip (1.4.1)
pyasn1 (0.1.7)
pycrypto (2.6.1)
python-dateutil (2.4.2)
PyYAML (3.11)
rsa (3.1.4)
setuptools (0.9.8)
simplejson (3.6.5)
six (1.9.0)
It doesn't even point out where the problem could be. Is there any way to
find out?
PS: I tried to delete the python virtualenv and recreate it back but the
issue still remains.
Regards,
Constantin
--
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/5a22280e-a6b4-4621-9d50-6375bf19682b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
