If I reverse the order, like this
- name: Wait for SSH to come up
local_action: wait_for host={{ item.public_dns_name }} port=22
delay=60 timeout=320 state=started
with_items: ec2.instances
- name: associate test.example.com with this instance
local_action: ec2_eip instance_id={{ item.id }} ip=54.123.243.14
region=us-east-1
with_items: ec2.instances
it gets through those ok, but hangs in the middle of the next stanza.
So assigning an Elastic IP address disturbs the environment.
mark
On Wednesday, April 16, 2014 4:42:29 PM UTC-5, mark david mcCreary wrote:
>
> My playbook looks like this
>
> ---
>
>>
>>
--
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/f1facf87-a1f9-464c-ac87-9a1be455a035%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
