For posterity... I downloaded a fresh copy of ec2.py today and this was no
longer an issue. In the new copy there was an 'if' that changed to an 'if
not' near the lines of the exception catch I had to comment out before, so
I'm assuming that was it.
On Wednesday, January 15, 2014 10:29:42 PM
Heh, was just looking at this...
I think boto is throwing a non-fatal exception that ec2.py is interpreting
as fatal. If I comment out the sys.exit call on line line
288https://github.com/ansible/ansible/blob/devel/plugins/inventory/ec2.py#L288I
still get the error message, but then the script
FWIW...here is that output...
bobtheuser@ip-172-20-fake-124:~/jobs/thajob/workspace/bin/devtools/ansible$
./ec2.py --list --refresh-cache
Looks like AWS is down again:
EC2ResponseError: 401 Unauthorized
?xml version=1.0 encoding=UTF-8?
ResponseErrorsErrorCodeAuthFailure/CodeMessageAWS was not
On Monday, January 13, 2014 3:57:52 PM UTC-8, Mark Casey wrote:
No change specifically with ec2.py... it doesn't work on the host where I
wanted to use it, but it does on another host I tried it on.
However, on the host where ec2.py is not working, I thought I'd mention
that I am able to
Thanks for all the great suggestions! Not sure if it will be today but I'll try
them and post back how I get on.
--
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
No change specifically with ec2.py... it doesn't work on the host where I
wanted to use it, but it does on another host I tried it on.
However, on the host where ec2.py is not working, I thought I'd mention
that I am able to use boto on the python shell:
ubuntu@ip-172-16-20-21:/etc/ansible$
Could it be a security group issue (have you limited your outbound ports
etc...?)?
Or DNS? Does the aws console resolved to the same place when digged from inside?
On 2014-01-13 16:57, Mark Casey wrote:
No change specifically with ec2.py... it doesn't work on the host where I
wanted to use
Check the version of boto. I ran into the same issue and found that the
version of boto on the system was old enough that it
wouldn't automatically pull in EC2 role credentials.
-Jharrod
On Monday, January 13, 2014 9:40:00 AM UTC-7, Mark Casey wrote:
I have a role that uses the ec2 module
