Hey,

Thanks for the quick reply. I did attach a floating Ip to the instance. To 
test, I took the instance created inside the Openstack and tried deploying the 
machine with the services:

Starting cluster using provider: ubuntu
... calling verify-prereqs
Deploying on machine 10.x.x.x

ubuntu@10.x.x.x’s password:
ubuntu@10.x.x.x’s password:
config-default.sh                                                               
                                           100% 2447     2.4KB/s   00:00

broken pipe
lost connection.

and that is it. It breaks the connection. I did add the port 22 through the 
manage rules in the security groups.



From: ICHIBA Sara [mailto:ichi.s...@gmail.com]
Sent: Wednesday, July 08, 2015 12:22 PM
To: Adyanthaya, Aishwarya
Cc: openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators] No route to host

hey,
It's probably because you forgot to open the port 22 of your instance using the 
security groups.
your ssh command says that it couldn't reach the host 10.x.x.x . are you trying 
to ssh into your machine B using its private IP ? if so try to assign a 
floating IP to your machine B and then try again with this FIP instead.
Cheers,
Sara

2015-07-08 7:55 GMT+02:00 
<aishwarya.adyanth...@accenture.com<mailto:aishwarya.adyanth...@accenture.com>>:
Hi,

I’m having trouble while trying to deploy a package from ‘machine-A’ outside 
openstack to the ‘machine-B’(instance) inside openstack which is created 
through the dashboard.

This is the error I get when I try to deploy it:
ssh: connect to host 10.x.x.x port 22: No route to host

Could anyone point out what I have to do to fix it.

Thank you,
Aishwarya Adyanthaya

________________________________

This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise confidential information. If you have received it in 
error, please notify the sender immediately and delete the original. Any other 
use of the e-mail by you is prohibited. Where allowed by local law, electronic 
communications with Accenture and its affiliates, including e-mail and instant 
messaging (including content), may be scanned by our systems for the purposes 
of information security and assessment of internal compliance with Accenture 
policy.
______________________________________________________________________________________

www.accenture.com<http://www.accenture.com>

_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org<mailto:OpenStack-operators@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Reply via email to