python-boto 2.34.0-2 is incompatible with backports ansible 2.0.2.0-1~bpo8+1

[Adam Baxter <voltagex@voltagex.org>]

Hi all,

Please CC me if you respond as I'm not subscribed to this list.

Upgrading Ansible from jessie-backports causes at least one bug with the ec2_ami_find module

Without setting up Ansible and a playbook, you can replicate the bug with the following script

#!/usr/bin/env python
from boto.ec2 import connect_to_region
ec2_connection = connect_to_region("us-west-2")
image = ec2_connection.get_all_images(owners="379101102735")[-1]
for k,v in vars(image).iteritems():
       print "{0}:{1}".format(k,v)


With the latest version of boto, there is no creationDate attribute on an EC2 AMI:

voltagex@kiwi:~/ansible$ python test_bug.py | grep creationDate
voltagex@kiwi:~/ansible$

Whereas running in a virtualenv with boto 2.40 leads to:

(latest-env)voltagex@kiwi:~/ansible$ python test_bug.py | grep creationDate
creationDate:2015-01-28T12:24:59.000Z

The Ansible bug occurs when the ec2_ami_find script tries to access this attribute without checking if it exists, and crashes.
https://github.com/ansible/ansible-modules-core/blob/devel/cloud/amazon/ec2_ami_find.py#L377

Could you please backport python-boto 2.40 to fix this issue?


Regards,
Adam Baxter