Weird idempotency issue with 2.0.2.0 on ec2_vpc module

Hello Guys,

I just upgraded and quickly got caught up with a weird issue with the ec2_vpc. It’s a existing playbook and worked fine. The weird part is that the playbook works fine the first type but give this error the subsequent times:

"An exception occurred during task execution. To see the full traceback, use -vvv. The error was: AttributeError: ‘NoneType’ object has no attribute ‘items’
fatal: [127.0.0.1]: FAILED! => {“changed”: false, “failed”: true, “module_stderr”: “Traceback (most recent call last):\n File "/home/joseph/.ansible/tmp/ansible-tmp-1461608488.65-217479095820231/ec2_vpc", line 2944, in \n main()\n File "/home/joseph/.ansible/tmp/ansible-tmp-1461608488.65-217479095820231/ec2_vpc", line 731, in main\n (vpc_dict, new_vpc_id, subnets_changed, igw_id, changed) = create_vpc(module, vpc_conn)\n File "/home/joseph/.ansible/tmp/ansible-tmp-1461608488.65-217479095820231/ec2_vpc", line 416, in create_vpc\n subnet_tags_extra = (set(csn.tags.items()).issubset(set(new_subnet_tags.items())))\nAttributeError: ‘NoneType’ object has no attribute ‘items’\n”, “module_stdout”: “”, “msg”: “MODULE FAILURE”, “parsed”: false}
"

If I delete the vpc and run the script again it works again but for the first type only. The command run is with a awscli profile:

AWS_PROFILE=test ansible-playbook aws_structure_playbook.yml on ubuntu trustry

the content of the playbook is on pastbin.com

This affects me. is there a way I can go back to the previous 2.0 version? could not see any in the apt-cache for the ppa.

Thanks