euca2ools generates an image that cannot be connected using ssh

[william_lin]

Binary package hint: euca2ools

Hi,

I'm using Eucalyptus 1.6
It seems like bundling from a running instance always generates an image that cannot be used(ssh doesn't work). Both euca2ools 1.0 & 1.2 do not work. Here are my steps:(using euca2ools 1.2)
1. launch an instance based on a default image(ubuntu, x86_64). Use ssh to connect to that instance.
2. In that instance have those pem files ready and execute "eucarc" to set up the environment variables.
3. Get euca2ools 1.2 thru "bzr co lp:eucalyptus/euca2ools-1.0". Install it and make sure "euca-version" command returns "1.2 ..." and /usr/share/pyshare/euca2ools/__init__.py is version 1.2 content.
4. Run these commands:
euca-bundle-vol -d /mnt -s 1024 -r x86_64 -e /tmp,/mnt,/root/.ssh,/home/ubuntu/.ssh
euca-upload-bundle -b testbucket2
euca-register testbucket2/image.manifest.xml
All 3 commands execute successfully.
5. Now launch an instance of the new created image. euca-describe-instances shows the instance is running. However, I cannot connect to the new instance using ssh.
6. Using euca-get-console-output on the new instance id will get:

...................
[ 0.715989] Write protecting the kernel text: 4592k
[ 0.716679] Write protecting the kernel read-only data: 1836k
Loading, please wait...
Couldn't get a file descriptor referring to the console
[ 0.984216] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
[ 0.984973] virtio-pci 0000:00:05.0: PCI INT A -> Link[LNKA] -> GSI 10 (level, high) -> IRQ 10
[ 0.990278] sym53c8xx 0000:00:04.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, high) -> IRQ 11
[ 0.992361] sym0: <895a> rev 0x0 at pci 0000:00:04.0 irq 11
[ 0.996280] Intel(R) PRO/1000 Network Driver - version 7.3.21-k3-NAPI
[ 0.997040] Copyright (c) 1999-2006 Intel Corporation.
Begin: Loading essential drivers... ...
Done.
Begin: Running /scripts/init-premount ...
[ 1.016564] sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
[ 1.020010] sym0: SCSI BUS has been reset.
[ 1.027904] scsi2 : sym-2.2.3
Done.
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Done.
Begin: Waiting for root file system... ...[ 1.067695] FDC 0 is a S82078B

[ 1.084294] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
[ 1.085001] e1000 0000:00:03.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, high) -> IRQ 11
[ 1.365867] e1000: 0000:00:03.0: e1000_probe: (PCI:33MHz:32-bit) d0:0d:5a:71:09:69
[ 1.403544] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
[ 4.028284] scsi 2:0:0:0: Direct-Access QEMU QEMU HARDDISK 0.11 PQ: 0 ANSI: 3
[ 4.029258] scsi target2:0:0: tagged command queuing enabled, command queue depth 16.
[ 4.030172] scsi target2:0:0: Beginning Domain Validation
[ 4.031021] scsi target2:0:0: Domain Validation skipping write tests
[ 4.031716] scsi target2:0:0: Ending Domain Validation
[ 4.034016] sd 2:0:0:0: Attached scsi generic sg1 type 0
[ 4.034727] sd 2:0:0:0: [sda] 4237312 512-byte logical blocks: (2.16 GB/2.02 GiB)
[ 4.035585] sd 2:0:0:0: [sda] Write Protect is off
[ 4.036211] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 4.037411] sda: sda1 sda2 sda3
[ 4.039201] sd 2:0:0:0: [sda] Attached SCSI disk
Done.
Gave up waiting for root device. Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/sda1 does not exist. Dropping to a shell!

Any idea?

Thanks
William

[Scott Moser (smoser)]

On Wed, 3 Mar 2010, william_lin wrote:

> I'm using Eucalyptus 1.6
> It seems like bundling from a running instance always generates an image that cannot be used(ssh doesn't work). Both euca2ools 1.0 & 1.2 do not work. Here are my steps:(using euca2ools 1.2)
> 1. launch an instance based on a default image(ubuntu, x86_64). Use ssh to connect to that instance.

Can you please give more information on "default image" ? If you're using
something from uec-images, please give the serial number (YYYYMMDD[.X]).
The guest image is as likely to be the source of the problem as the tool.

[william_lin (william-lin)]

Hi,

 Currently the Store tab shows nothing(weird)
 From Images tab I could see
 emi-DF01106E image-store-1265841703/image.manifest.xml eki-F52310EA eri-09A21158

 Is this info useful?

Regards
William

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Scott Moser
Sent: Wednesday, March 03, 2010 6:02 AM
To: William Lin (RD-US)
Subject: Re: [Bug 531111] [NEW] euca2ools generates an image that cannot beconnected using ssh

On Wed, 3 Mar 2010, william_lin wrote:

> I'm using Eucalyptus 1.6
> It seems like bundling from a running instance always generates an
> image that cannot be used(ssh doesn't work). Both euca2ools 1.0 & 1.2 do not work. Here are my steps:(using euca2ools 1.2) 1. launch an instance based on a default image(ubuntu, x86_64). Use ssh to connect to that instance.

Can you please give more information on "default image" ? If you're using something from uec-images, please give the serial number (YYYYMMDD[.X]).
The guest image is as likely to be the source of the problem as the tool.

--
euca2ools generates an image that cannot be connected using ssh
https://bugs.launchpad.net/bugs/531111
You received this bug notification because you are a direct subscriber of the bug.

Status in "euca2ools" package in Ubuntu: New

Bug description:
Binary package hint: euca2ools

Hi,

I'm using Eucalyptus 1.6
It seems like bundling from a running instance always generates an image that cannot be used(ssh doesn't work). Both euca2ools 1.0 & 1.2 do not work. Here are my steps:(using euca2ools 1.2) 1. launch an instance based on a default image(ubuntu, x86_64). Use ssh to connect to that instance.
2. In that instance have those pem files ready and execute "eucarc" to set up the environment variables.
3. Get euca2ools 1.2 thru "bzr co lp:eucalyptus/euca2ools-1.0". Install it and make sure "euca-version" command returns "1.2 ..." and /usr/share/pyshare/euca2ools/__init__.py is version 1.2 content.
4. Run these commands:
euca-bundle-vol -d /mnt -s 1024 -r x86_64 -e /tmp,/mnt,/root/.ssh,/home/ubuntu/.ssh
euca-upload-bundle -b testbucket2
euca-register testbucket2/image.manifest.xml All 3 commands execute successfully.
5. Now launch an instance of the new created image. euca-describe-instances shows the instance is running. However, I cannot connect to the new instance using ssh.
6. Using euca-get-console-output on the new instance id will get:

...................
[ 0.715989] Write protecting the kernel text: 4592k
[ 0.716679] Write protecting the kernel read-only data: 1836k
Loading, please wait...
Couldn't get a file descriptor referring to the console
[ 0.984216] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
[ 0.984973] virtio-pci 0000:00:05.0: PCI INT A -> Link[LNKA] -> GSI 10 (level, high) -> IRQ 10
[ 0.990278] sym53c8xx 0000:00:04.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, high) -> IRQ 11
[ 0.992361] sym0: <895a> rev 0x0 at pci 0000:00:04.0 irq 11
[ 0.996280] Intel(R) PRO/1000 Network Driver - version 7.3.21-k3-NAPI
[ 0.997040] Copyright (c) 1999-2006 Intel Corporation.
Begin: Loading essential drivers... ...
Done.
Begin: Running /scripts/init-premount ...
[ 1.01656...

[Dave Walker (davewalker)]

@Mitch, do you know if this is still an issue with current euca2ools in trunk?

Thanks.

[Mitch Garnaat (mitch-garnaat)]

I need to run some tests to verify that this is no longer a problem in euca2ools 2.0. I'll do that over the weekend and report back on Monday.