Upgrade to Ubuntu 15.10 Broken: lxc-net.service fails on upgrade
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Release Notes for Ubuntu |
Undecided
|
Unassigned | ||
| | lxc (Ubuntu) |
Undecided
|
Unassigned | ||
Bug Description
With lxc installed, the 15.04 -> 15.10 upgrade fails. The upgrade completes if LXC is removed and then reinstalled later. Here is me using apt to try and make it work (gives same errors as upgrade-manager did):
Setting up lxc (1.1.4-0ubuntu1) ...
Job for lxc-net.service failed because the control process exited with error code. See "systemctl status lxc-net.service" and "journalctl -xe" for details.
invoke-rc.d: initscript lxc-net, action "start" failed.
dpkg: error processing package lxc (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of lxc-templates:
lxc-templates depends on lxc (>= 0.8.0~rc1-
Package lxc is not configured yet.
dpkg: error processing package lxc-templates (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
lxc
lxc-templates
E: Sub-process /usr/bin/dpkg returned an error code (1)
╭─michael@
╰─$ systemctl status lxc-net.service 100 ↵
● lxc-net.service - LXC network bridge setup
Loaded: loaded (/lib/systemd/
Active: failed (Result: exit-code) since Thu 2015-10-22 12:50:07 AEDT; 27s ago
Process: 22655 ExecStart=
Main PID: 22655 (code=exited, status=1/FAILURE)
Oct 22 12:50:07 michael-
Oct 22 12:50:07 michael-
Oct 22 12:50:07 michael-
Oct 22 12:50:07 michael-
Oct 22 12:50:07 michael-
Oct 22 12:50:07 michael-
| Martin Pitt (pitti) wrote : | #1 |
| affects: | lxc → lxc (Ubuntu) |
| summary: |
- Upgrade to Ubuntu 15.10 Broken + Upgrade to Ubuntu 15.10 Broken: lxc-net.service fails on upgrade |
| Serge Hallyn (serge-hallyn) wrote : | #2 |
Please show the results of
sudo systemctl status lxc-net.service
sudo journalctl -u lxc-net
sudo journalctl -xe
ifconfig -a
cat /etc/default/
| Changed in lxc (Ubuntu): | |
| status: | New → Incomplete |
| Adam Stokes (adam-stokes) wrote : | #3 |
I hit this too, I actually just had to run:
/usr/lib/
And it seemed to put itself back into a state that systemd could work with
| Serge Hallyn (serge-hallyn) wrote : | #4 |
Was yours also on an upgrade from vivid to wily? Were you using the stock archive lxc packages? Any customizatoin of the lxc-net configuration?
| md_5 (md-5) wrote : | #5 |
Info is attached. Note that it is from 15.10 and working fine.
| Julian Edwards (julian-edwards) wrote : | #6 |
I was getting this too. I say was, because Adam's tip helped me resolve it. I'll also note that this is on a machine still running vivid.
| Robie Basak (racb) wrote : | #7 |
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.
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.
| Serge Hallyn (serge-hallyn) wrote : | #8 |
Tried to reproduce by installing lxc version from vivid release, then upgrading to -updates, but it worked fine :(
| Changed in ubuntu-release-notes: | |
| status: | New → Incomplete |
| Launchpad Janitor (janitor) wrote : | #9 |
[Expired for lxc (Ubuntu) because there has been no activity for 60 days.]
| Changed in lxc (Ubuntu): | |
| status: | Incomplete → Expired |
| Changed in ubuntu-release-notes: | |
| status: | Incomplete → New |
| Changed in lxc (Ubuntu): | |
| status: | Expired → New |


At first sight I thought this was a duplicate of bug 1504897, but that doesn't seem to be it. If lxc-net.service fails, then the problem is something else.