[Openstack-operators] Ansible-OpenStack:cannot ssh into the containers

Jesse Pretorius jesse.pretorius at gmail.com
Fri Nov 27 09:58:31 UTC 2015


On 24 November 2015 at 17:02, Achi Hamza <h16mara at gmail.com> wrote:

> Hi,
>
> I am trying to deploy openstack using openstack-ansible project. I am
> using Liberty release (tag *12.0.0*).
> The problem i have is that Ansible is not able to SSH into the containers:
>
> *TASK: [Wait for ssh to be available]
> ****************************************** *
> failed: [infra01_neutron_server_container-4d09aa86 -> 127.0.0.1] =>
> {"elapsed": 301, "failed": true}
> msg: Timeout when waiting for search string OpenSSH in 172.29.236.216:22
> failed: [infra01_utility_container-4da899df -> 127.0.0.1] => {"elapsed":
> 301, "failed": true}
> msg: Timeout when waiting for search string OpenSSH in 172.29.237.186:22
> failed: [infra01_neutron_agents_container-bd7aded5 -> 127.0.0.1] =>
> {"elapsed": 301, "failed": true}
> msg: Timeout when waiting for search string OpenSSH in 172.29.237.90:22
> failed: [infra01_memcached_container-12186fcf -> 127.0.0.1] => {"elapsed":
> 301, "failed": true}
> msg: Timeout when waiting for search string OpenSSH in 172.29.238.177:22
> failed: [infra01_rabbit_mq_container-7103e2f2 -> 127.0.0.1] => {"elapsed":
> 301, "failed": true}
> msg: Timeout when waiting for search string OpenSSH in 172.29.238.178:22
> failed: [infra01_galera_container-b691e13b -> 127.0.0.1] => {"elapsed":
> 301, "failed": true}
> msg: Timeout when waiting for search string OpenSSH in 172.29.236.60:22
> failed: [infra01_nova_conductor_container-98abf1df -> 127.0.0.1] =>
> {"elapsed": 301, "failed": true}
> msg: Timeout when waiting for search string OpenSSH in 172.29.238.8:22
> failed: [infra01_horizon_container-5756dc20 -> 127.0.0.1] => {"elapsed":
> 301, "failed": true}
> msg: Timeout when waiting for search string OpenSSH in 172.29.236.47:22
> failed: [infra01_nova_cert_container-17a8689a -> 127.0.0.1] => {"elapsed":
> 301, "failed": true}
> .........
> .........
> .........
>
>
> I can ping the containers:
>
>
> *root at infra01:~# ping infra01_galera_container-b691e13bPING
> infra01_galera_container-b691e13b (172.29.236.60) 56(84) bytes of data.*
> 64 bytes from infra01_galera_container-b691e13b (172.29.236.60):
> icmp_seq=1 ttl=64 time=0.103 ms
> 64 bytes from infra01_galera_container-b691e13b (172.29.236.60):
> icmp_seq=2 ttl=64 time=0.086 ms
> 64 bytes from infra01_galera_container-b691e13b (172.29.236.60):
> icmp_seq=3 ttl=64 time=0.110 ms
>

Hi Amza,

My apologies for only getting back to you right now.

We've been seeing similar SSH connectivity issues in gate checks and have
what we believe is a solution in a review in flight [1]. The patch is
easily implemented in your environment.

Failing that I have a few suggestions:

1 - Implement using at least the tag 12.0.1 as we fixed some pretty crucial
release bugs between 12.0.0 and 12.0.1. You can also implement from the
head of the Liberty branch.
2 - If your host(s) are a little slow you may wish to implement an
increased delay in /etc/openstack_deploy/user_variables.yml using the
variable 'ssh_delay'.
3 - If possible, try and catch us in the Freenode IRC channel
#openstack-ansible - there're often people there who can help you
troubleshoot.

[1] https://review.openstack.org/249942
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20151127/b02d9a01/attachment.html>


More information about the OpenStack-operators mailing list