I'm not sure if it's my setup or because of a recent change in libvirt
or lxc but I'm still having the resize error on a lxc container:
2012-02-25 21:46:53,755 - __init__.py[DEBUG]: handling resizefs with freq=None
and args=[]
2012-02-25 21:46:53,764 - cc_resizefs.py[WARNING]: Failed to make devi
I have a similar problem so I think the bug is still there. I can
provide more info if you want.
I'm running libvirt in a rackspace server.
00:49:55.700: 3071: info : libvirt version: 0.9.2
00:49:55.700: 3071: error : virCommandWait:1393 : internal error Child process
(/sbin/iptables --table man
Public bug reported:
ii nova-ajax-console-proxy 2011.3-0ubuntu6.2
OpenStack Compute - AJAX console proxy
ii nova-api 2011.3-0ubuntu6.2
OpenStack Compute - API frontend
ii nova-common 2011.3-0u
** Attachment added: "crash_libvirt_lxc.trace"
https://bugs.launchpad.net/bugs/887859/+attachment/2590178/+files/crash_libvirt_lxc.trace
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs
I fixed the problem. I forgot to mount rootfs of the lxc container
before doing the euca-reboot-instance...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/887859
Title:
euca-reboot-ins
** Project changed: lxc => lxc (Ubuntu)
** Description changed:
At least in versions:
release: saucy
- lxc: 1.0.0~alpha1-0ubuntu2
- juju-core: 1.13.3-0ubuntu1
+ lxc: 1.0.0~alpha1-0ubuntu4
- after the lxc-destroy command, symlinks are still there.
+ after the lxc-destroy command, symlink
