This repository has been archived by the owner on Oct 30, 2018. It is now read-only.
ec2_vpc doesn't create subnets correctly #2930
Labels
Comments
Adding @autotune as he worked on the commit. |
Hey Ryan, Thanks for the heads up. I will look into replicating this issue and fixing as soon as I have time available. Will also keep this thread updated as I look into it and see where we can go from here. |
Any updates on this. |
It was merged into |
This bug may mess with the entire subnet tagging of the user. I experienced myself using v2.0.1.0-1, fortunately did on an isolated vpc. It would be nice if we could release this one ASAP |
Thanks everyone. Closing as fixed in devel (will be 2.1.0) via #2931 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue Type:
Bug Report
Ansible Version:
From Source
Master
ansible 2.1.0
Ansible Configuration:
Not changes
Environment:
Mac OSX Yosimite
Summary:
The ec2_vpc module seems to be broken. Subnet creation is no longer idempotent and it seems to be overwriting things incorrectly. I have narrowed the issue down to the following commit. I am trying to resolve the issue, but I haven't done too much python.
Steps to reproduce:
I am creating a VPC in AWS using Ansible. The following play is run
First time around this creates everything perfectly. Second time around, I expect it to not do anything as everything has been created, however, the public subnet is updated to a private one.
Here are the variables:
Also just to clarify on what change is happening. All the resource tags of the one subnet (public) are being overwritten with the tags of another subnet (private).
I have narrowed this down to the following commit.
The text was updated successfully, but these errors were encountered: