Comment 7 for bug 1508744

I hit what I think might be this issue on Vivid, just doing an upgrade to the latest lxc in vivid-updates because I was hitting a separate bug (I'll file next) and thought updating to the latest vivid-updates might fix it. In my case, "service lxc-net stop" succeeded, but "service lxc-net start" still did not work. Rebooting fixed it.

I didn't keep many logs (sorry), but the original versions on Vivid and the versions I upgraded to were:

Commandline: apt-get install lxc
Upgrade: lxc:amd64 (1.1.2-0ubuntu3, 1.1.5-0ubuntu0.15.04.3), python3-lxc:amd64 (1.1.2-0ubuntu3, 1.1.5-0ubuntu0.15.04.3), liblxc1:amd64 (1.1.2-0ubuntu3, 1.1.5-0ubuntu0.15.04.3)
Error: Sub-process /usr/bin/dpkg returned an error code (1)

So perhaps this might be reproducible from a Vivid machine that is on the release pocket only, adding the -updates pocket and then "sudo apt-get install lxc". I haven't tried this though.

I hope that's helpful.