Comment 24 for bug 924337

Is it possible that this bug returned?

I updated the host to ubuntu saucy and lxc was working fine with the virtual machine "jenkins". Once I updated the guest system to saucy as well, it seemed not to boot, but I was wrong. It never reached the runlevel (5), which it did before.

Here is the output of lxc-ls

# lxc-ls --fancy
NAME STATE IPV4 IPV6 AUTOSTART
-------------------------------------------------
jenkins RUNNING 192.168.1.30 - NO
php-54-32 STOPPED - - NO
test STOPPED - - NO

as you can see it is running, but not reachable by ssh. so I entered:

# lxc-attach -n jenkins -- runlevel
unknown

it doesn't know in which runlevel it is.

even though the network is up within the guest system:

# lxc-attach -n jenkins -- ifconfig
eth0 Link encap:Ethernet HWaddr 10:16:3e:53:5b:7a
          inet addr:192.168.1.30 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::1216:3eff:fe53:5b7a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:277 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:44733 (44.7 KB) TX bytes:648 (648.0 B)

as soon as I force the runlevel with:

lxc-attach -n jenkins -- init 5

everything is working, until I reboot the guest again.