Not able to ssh into RDO Kilo instance [closed]

asked 2015-10-26 12:26:24 -0600

Jatin gravatar image

I've created an RDO Kilo Instance on a centos 7 vm using the RDO project Quick-start guide. I am able to create an instance from a Fedora22 image, but not able to ssh into the instance. I have checked the following things while creating the instance:

  1. Added rule for port 22 in the Security Group.
  2. Associated a floating IP with the instance.
  3. Imported a key pair to create the instance.

Below is the log for the instance:

[ [31m*[1;31m*[0m[31m*  [0m] A start job is running for LSB: Bring up/down networking (56s / 5min 17s)[K[[31m*[1;31m*[0m[31m*   [0m] A start job is running for LSB: Bring up/down networking (56s / 5min 17s)[K[[1;31m*[0m[31m*    [0m] A start job is running for LSB: Bring up/down networking (57s / 5min 17s)[K[[0m[31m*     [0m] A start job is running for LSB: Bring up/down networking (57s / 5min 17s)[K[[1;31m*[0m[31m*    [0m] A start job is running for LSB: Bring up/down networking (58s / 5min 17s)[K[[31m*[1;31m*[0m[31m*   [0m] A start job is running for LSB: Bring up/down networking (58s / 5min 17s)[K[ [31m*[1;31m*[0m[31m*  [0m] A start job is running for LSB: Bring up/down networking (59s / 5min 17s)[K[  [31m*[1;31m*[0m[31m* [0m] A start job is running for LSB: Bring up/down networking (59s / 5min 17s)[K[   [31m*[1;31m*[0m[31m*[0m] A start job is running for LSB: Bring up/down networking (1min / 5min 17s)[K[    [31m*[1;31m*[0m] A start job is running for LSB: Bring up/down networking (1min / 5min 17s)[K[     [31m*[0m] A start job is running for LSB: Bring up/down networking (1min 1s / 5min 17s)[K[    [31m*[1;31m*[0m] A start job is running for LSB: Bring up/down networking (1min 1s / 5min 17s)[K[   [31m*[1;31m*[0m[31m*[0m] A start job is running for LSB: Bring up/down networking (1min 2s / 5min 17s)[K[  [31m*[1;31m*[0m[31m* [0m] A start job is running for LSB: Bring up/down networking (1min 2s / 5min 17s)[K[ [31m*[1;31m*[0m[31m*  [0m] A start job is running for LSB: Bring up/down networking (1min 3s / 5min 17s)[K[[31m*[1;31m*[0m[31m*   [0m] A start job is running for LSB: Bring up/down networking (1min 3s / 5min 17s)[K[[1;31m*[0m[31m*    [0m] A start job is running for LSB: Bring up/down networking (1min 4s / 5min 17s)[K[[0m[31m*     [0m] A start job is running for LSB: Bring up/down networking (1min 4s / 5min 17s)[K[[1;31m*[0m[31m*    [0m] A start job is running for LSB: Bring up/down networking (1min 5s / 5min 17s)[K[[32m  OK  [0m] Started LSB: Bring up/down networking.
[[32m  OK  [0m] Reached target Network is Online.
         Starting Initial cloud-init job (metadata service crawler)...
[   95.728280] cloud-init[588]: Cloud-init v. 0.7 ...
(more)
edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by rbowen
close date 2016-06-21 13:53:47.810688

Comments

It looks like the instance itself did get an IP, so this boils it down to an issue between either you and the router, or the router and the instance. There's some tips in a talk I gave a while ago: http://assafmuller.com/2015/08/31/neu.... I hope this helps, keep us updated :)

Assaf Muller gravatar imageAssaf Muller ( 2016-01-11 20:55:42 -0600 )edit

Just to rule out any issues with the floating-ip. Considering that VM was able to acquire IP successfully, can you try ssh to the VM from the router/dhcp namespace?

sridhargaddam gravatar imagesridhargaddam ( 2016-03-31 06:04:37 -0600 )edit

Kilo is now EOL. Please reopen if you're having this difficulty on a more recent, supported version of OpenStack.

rbowen gravatar imagerbowen ( 2016-06-21 13:53:42 -0600 )edit