[
https://issues.apache.org/jira/browse/METRON-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382313#comment-15382313
]
David M. Lyle commented on METRON-85:
-------------------------------------
[~nickwallen] fixed this as part of:
28cd32c6ff2f997e23950c99c3ce8ffff3487fb2
METRON-132 Monit integration + METRON-85 Removed fixed wait from EC2 deployment
(nickwallen) closes apache/incubator-metron#118
> wait_for in check_hosts.yml deployment script should specify port and perhaps
> regex
> -----------------------------------------------------------------------------------
>
> Key: METRON-85
> URL: https://issues.apache.org/jira/browse/METRON-85
> Project: Metron
> Issue Type: Bug
> Reporter: David M. Lyle
> Priority: Minor
> Labels: deployment
>
> Currently, the wait_for on line 19 of
> deployment/amazon-ec2/tasks/check-hosts.yml doesn't specify a port. Ansible
> simply sleeps for the default timeout in this case (5 minutes).
> This wasn't as intended. The deployment should continue as soon as all hosts
> are able to accept incoming ssh connections.
> One thing- there was a corner case revealed in testing where:
> - name: Wait for connectivity to host(s)
> wait_for: host={{ item.public_dns_name }} port=22 search_regex=OpenSSH
> with_items: ec2.tagged_instances
> when: item.public_dns_name is defined
> actually allowed execution to continue before some of the hosts started
> accepting external SSH connections, causing the deployment to fail. So, in
> addition to checking for port 22 to be up, there may additional work
> required- perhaps making that a local action.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
