openstack team mailing list archive

[Muhammad Atif <m_atif_s@xxxxxxxxx>]

Hi Openstack gurus,

We have recently shifted from eucalyptus to openstack and so far, finding it 
quite stable. However, we are having terrible time re-bundling an existing 
image. 

The re-bundled image is able to complete the boot process upto mountall: but the 
cloud-init never fires up.

Here is what we have done so far, please let us know what exactly is wrong on 
our side.

1- Downloaded the ubuntu1010 image from openstack site as follows: 
    wget 
http://c0179148.cdn1.cloudfiles.rackspacecloud.com/ubuntu1010-UEC-localuser-image.tar.gz

2- publish this image:
uec-publish-tarball ubuntu1010-UEC-localuser-image.tar.gz ubuntu x86_64
3- Now we run the image using euca-run-instance and it boots up fine, we are 
also able to login using the private key and able to install software.

4- When we want to save the instace into an image (rebundle), following sequence 
is performed

    -   rm -r /etc/udev/rules.d/70-*

    -   copy the nove certificates and source .novarc

    -   euca-bundle-vol -c ${EC2_CERT} -k ${EC2_PRIVATE_KEY} -u ${EC2_USER_ID} 
--ec2cert ${NOVA_CERT} --no-inherit --kernel aki-00000XXX -d /mnt -r x86_64 -p 
ubuntu-1010-rebundle -s 2048 -e /var/lib/dhcp3 


    -  euca-upload-bundle -b ubuntu -m  /mnt/ubuntu-1010-rebundle.manifest.xml

   -  euca-register ubuntu/ubuntu-1010-rebundle.manifest.xml

5- Now we fire up this image once it has been successfully uploaded; we get 
stuck after plymouth-splash. Comapred to the original image which started 
cloud-init after this point. The image is replying to pings but refusing ssh. It 
can be some odd ssh key issue?

[    0.384064] md: autorun ...
[    0.384435] md: ... autorun DONE.
[    0.386063] EXT3-fs: barriers not enabled
[    0.386946] kjournald starting.  Commit interval 5 seconds
[    0.387731] EXT3-fs (vda): mounted filesystem with ordered data mode
[    0.388644] VFS: Mounted root (ext3 filesystem) readonly on device 252:0.
[    0.389738] devtmpfs: mounted
[    0.390218] Freeing unused kernel memory: 828k freed
[    0.391214] Write protecting the kernel read-only data: 10240k
[    0.392153] Freeing unused kernel memory: 308k freed
[    0.393078] Freeing unused kernel memory: 1612k freed
mountall: Disconnected from Plymouth
init: plymouth main process (48) killed by SEGV signal
init: plymouth-splash main process (323) terminated with status 2


Any help is greatly appreciated. I am willing to provide you with other logs if 
requested.  



Regards,
Atif