I'm not an ec2 user but I wonder if it might be possible to adapt the
approach used here to wait for a webservice to return:
https://groups.google.com/forum/#!topic/ansible-project/iLjIbsCASWU
In that case he's using uri with an 'until' and using the 'default' filter
to make sure no results
I just discovered this issue as well, with various random ssh connection or
generic authentication/permission failure messages, some occurring after a
play successfully passed a task or two. It occurred very consistently with
many CentOS 7 t2.nano hosts. A 2-minute pause after waiting for ssh
This is what I do, to make sure that SSH comes up, but also wait until the
user has been created on my instance.
- set_fact:
ec2_ip: "{{ ec2_name | get_instance(aws_region, state='running') }}"
- name: Wait for SSH to come up on instance
wait_for:
host: "{{ ec2_ip }}"
port: 22
I am having this same issue. Did you ever figure out a solution?
I have 3 different images I'm testing against: CentOS6, CentOS7, Sles12.
The strange thing is that I only seem to have a problem on CentOS7.
On Monday, January 25, 2016 at 2:07:14 PM UTC-7, James Cuzella wrote:
>
> Hello,
>
> I
