OpenStack Compute (nova)

Ping or ssh failed when libvirt_type is lxc

Bug #753292 reported by guanxiaohua2k6
This bug report is a duplicate of:  Bug #757752: LXC containers do not start anymore.. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Undecided
Unassigned

Bug Description

I tried to run nova on ec2. I do the sames as what is said in the page http://zulcss.wordpress.com/2011/03/31/running-nova-openstack-on-amazon-ec2/. I succeed to install nova and run instance when libvirt type is lxc. But I failed to ping or ssh. Also I tried the same thing in the local machine, the result is same.

The related info is as followings.

1. Version
2011.2~bzr949-0ubuntu0ppa1~maverick1

2. OS
ubuntu natty

3. Image
natty-server-uec-amd64.tar.gz

4. Error log
I didn't found any error message in nova-*.log.

Thanks.

Revision history for this message
Thierry Carrez (ttx) wrote :

I have a few issues SSHing in (apparently issues in the Natty image or cloud-init process) but I manage to ping (after waiting for a bit).

Are you sure the LXC container is started ? A second "init" process should appear on the process table.

Changed in nova:
status: New → Incomplete
Revision history for this message
guanxiaohua2k6 (guanxiaohua2k6) wrote :

Yes, Thierry, just as what you said, after waiting for a moment, I can ping. I confirmed process table. There were two "init" processes.

Revision history for this message
Thierry Carrez (ttx) wrote :

OK, that's an image issue, not an OpenStack issue. Ubuntu is working on it, should have the fix for beta2.

Changed in nova:
status: Incomplete → Invalid
Revision history for this message
guanxiaohua2k6 (guanxiaohua2k6) wrote :

Thank you very much, Thierry.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.