Comment 6 for bug 1000174

also, before installing mdadm, I did let a bunch of updates install, and
I think it may have complained then as well, but I had to get some work
done, and everything else seemed ok. Then when I needed mdadm to test
an external raid box, this is when I had time to investigate further.
sorry I don't have any further info on when the problem may have first
occurred.

On 05/16/2012 11:04 AM, Serge Hallyn wrote:
> Thanks for reporting this bug. Interesting - so installing mdadm
> stopped lxc from starting? I can't reproduce that here, unfortunately.
>
> Do you have autostart containers defined? (what does ls -l
> /etc/lxc/auto show?)
>
> Can you add the line:
>
> console output
>
> right underneath the 'stop on' lines in both /etc/init/lxc.conf and
> /etc/init/lxc-net.conf, then do
>
> stop lxc
> start lxc
>
> and show the output here?
>
> ** Changed in: lxc (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: lxc (Ubuntu)
> Status: New => Incomplete
>