We ran into something similar a few days ago but I haven't had time to dig into the ec2_group code that much to figure it out.
I'm not sure if this is helpful, but if we had 'TCP' in all caps in the playbook it would behave like this (run fine the first time, create the group, etc., but on second attempt it would give the same error you were seeing). If I just changed it to 'tcp' all lower case the playbook ran fine. On Thursday, January 15, 2015 at 5:54:45 AM UTC-7, Nicolas G wrote: > > hi, > > I think when I was trying the ec2_group module for some reason it will > only fail if the security group already exists but was not created by the > module, if you create a new security group using the ec2_group module it > wont fail when you run the same playbook again. > > On Wednesday, January 14, 2015 at 10:22:35 AM UTC+2, Tzach Livyatan wrote: >> >> newbie Ansible ec2 question: >> I'm successfully using ec2_group_module [1] to create EC2 security group. >> However, the operation fail if the group is already there >> What is the idiomatic to conditionally skip it if the group is already >> there? >> >> Thanks >> >> >> [1] http://docs.ansible.com/ec2_group_module.html >> > -- 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/ca30c911-f728-434a-95a8-a3ad92b19e88%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
