Instance spawn ok but no ouput on the console, no ping, no ssh ...

Asked by Melicloud

Ive done a couple of installs of nova, but ive done a fresh install via scripted installation, single node, ubuntu + kvm for testing, everything works ok, i downloaded a tty image for testing purpouses, the instance run ok, but when i try to connect nothing happens and if you run a euca-get-console-output only shows the date and time ...

NOTE: the images are stored on a glance separated node , i uploaded as raw image

euca-describe-instances
RESERVATION r-h6des982 testhybrid default
INSTANCE i-00000001 ami-00000006 10.0.0.2 10.0.0.2 running testhybrid (testhybrid, kvmcontroller) 0 m1.small 2011-05-16T14:55:54Znova

euca-get-console-output i-00000001
i-00000001
2011-05-16T15:10:03Z

I created the machine via euca run : euca-run-instances ami-00000006 -k testhybrid -t m1.small

If i list the glance images :

euca-describe-images
IMAGE ami-00000001 None (Ubuntu Maverick 10.10) killed public machine
IMAGE ami-00000002 None (GIGZ) killed public machine
IMAGE ami-00000003 None (GIGZ) killed public machine
IMAGE ami-00000004 None (GIGZ) available public machine
IMAGE ami-00000005 None (Ubuntu Server Mav 10.10) available public machine
IMAGE ami-00000006 None (tty linuz) available public machine

Theres no errors in the nova-compute.log so im kinda lost, this happens to me in every environment ive installed. Multinode and this single-node

Anyhone has a clue ?

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Solved by:
Melicloud
Solved:
Last query:
Last reply:
Revision history for this message
Jordan Rinke (jordanrinke) said :
#1

Have you done the euca-authorize commands? Try running

euca-authorize -P icmp -t -1:-1 default
euca-authorize -P tcp -p 22 default

Revision history for this message
Vish Ishaya (vishvananda) said :
#2

blank console means the image is not booting properly. Either
a) you are trying to run a 64 bit image on a 32 bit host
or
b) your image was not uploaded correctly.

If it is the tty linux uec image, I would suggest you upload kernel ramdisk and image separately using uec-publish-tarball or nova-manage image all_register

Vish

On May 16, 2011, at 8:15 AM, Melicloud wrote:

> New question #157757 on OpenStack Compute (nova):
> https://answers.launchpad.net/nova/+question/157757
>
> Ive done a couple of installs of nova, but ive done a fresh install via scripted installation, single node, ubuntu + kvm for testing, everything works ok, i downloaded a tty image for testing purpouses, the instance run ok, but when i try to connect nothing happens and if you run a euca-get-console-output only shows the date and time ...
>
> NOTE: the images are stored on a glance separated node , i uploaded as raw image
>
>
> euca-describe-instances
> RESERVATION r-h6des982 testhybrid default
> INSTANCE i-00000001 ami-00000006 10.0.0.2 10.0.0.2 running testhybrid (testhybrid, kvmcontroller) 0 m1.small 2011-05-16T14:55:54Znova
>
> euca-get-console-output i-00000001
> i-00000001
> 2011-05-16T15:10:03Z
>
>
> I created the machine via euca run : euca-run-instances ami-00000006 -k testhybrid -t m1.small
>
> If i list the glance images :
>
> euca-describe-images
> IMAGE ami-00000001 None (Ubuntu Maverick 10.10) killed public machine
> IMAGE ami-00000002 None (GIGZ) killed public machine
> IMAGE ami-00000003 None (GIGZ) killed public machine
> IMAGE ami-00000004 None (GIGZ) available public machine
> IMAGE ami-00000005 None (Ubuntu Server Mav 10.10) available public machine
> IMAGE ami-00000006 None (tty linuz) available public machine
>
>
> Theres no errors in the nova-compute.log so im kinda lost, this happens to me in every environment ive installed. Multinode and this single-node
>
> Anyhone has a clue ?
>
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).

Revision history for this message
Jordan Rinke (jordanrinke) said :
#3

Also if you are using glance and using the tarball to upload glance doesn't unpack it like a euca-upload-bundle does... you would need to untar it and do the following...

glance add name=ramdisk disk_format=ari container_format=ari is_public=True < tty/ramdisk/image
glance add name=kernel disk_format=aki container_format=aki is_public=True < tty-kernel/image
glance add name=tty_ami disk_format=ami container_format=ami is_public=True ramdisk_id=<ramdisk ID> kernel_id=<kernel ID> < tty-machine/image

or something similar to upload each piece and associate it with the machine image.

Revision history for this message
Melicloud (it-tech) said :
#4

Uploading separately do the trick ! Thank u all guys !