I am getting the same problem. Ansible seems to be iterating over each
letter in a subnet id looking for duplicate letters. Not very helpful
validation. You would think unit tests would catch this before deployment,
but they probably used a string that has no duplicate letters...
On Friday, March 20, 2015 at 4:40:16 AM UTC-7, Arangel Angov wrote:
>
> Hello,
>
> I wasn't able to find any reference to this so far so here it goes:
>
> I have a playbook that creates a new autoscaling group
>
> ec2_asg:
> name: "{{ asg_name }}"
> region: "us-east-1"
> availability_zones: "us-east-1b,us-east-1c,us-east-1d,us-east-1e"
> vpc_zone_identifier: [ 'subnet-xxxxxxxx', 'subnet-xxxxxxxx',
> 'subnet-xxxxxxxx', 'subnet-xxxxxxxx' ]
> launch_config_name: "xxxxxxxx-{{ unique_id }}"
> health_check_period: 60
> health_check_type: ELB
> min_size: 2
> max_size: 8
> desired_capacity: 2
> replace_all_instances: yes
> load_balancers: "{{ load_balancer }}"
> wait_timeout: 600
>
> I'm getting the following error on the task when running the playbook:
>
> msg: BotoServerError: 400 Bad Request
> <ErrorResponse xmlns="http://autoscaling.amazonaws.com/doc/2011-01-01/";>
> <Error>
> <Type>Sender</Type>
> <Code>ValidationError</Code>
> <Message>Duplicate subnets specified: [x, x, x, x, ', ', s, u, b, n,
> e, t, -, x, x, x, x, ,x x, ', ', s, u, b, n, e, t, -, x, x, x, x, x, ', ',
> s, u, b, n, e, t, -, x, x, x, x, x, x, ']</Message>
> </Error>
> <RequestId>xxxxxxxxxxxxxxxxxxxxxxx</RequestId>
> </ErrorResponse>
>
>
> I've double-checked my subnets and they are unique.
>
> According to the example in the documentation, the value for
> vpc_zone_identifier should always be a list.
>
>
> Anyone seen this before or now with Ansible 1.8.4?
>
> Thanks.
>
> --
> *Arangel*
>
> *Disclaimer*
>
> This email is really important (well, most of them are.). Also, hopefully
> the message has been sent to the person it’s intended for. If we stuffed up
> by entering the wrong email address, we’re very sorry for cluttering up
> your inbox. But if we have done that, then please do us a favour and let us
> know…and if you could keep the juicy bits to yourself, that would be great
> too.
>
> Also…stuff that’s said in this message are the views of the person writing
> the email and do not actually represent the views of GetSocial (although
> they might, but we’re just hedging our bets here). Don’t think for one
> minute that anything in this message should be construed as creating a
> contract.
>
> GetSocial owns the email infrastructure, including the contents.
>
> Finally…do the right thing by the environment and “think before you ink”!
>
> **********************************************************************
>
--
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/04a25719-1a1e-4a27-8383-95d4991e0a0d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
