lxc packaging w/ bridge-utils is confused

Bug #1281793 reported by Tycho Andersen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxc (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

CloudFive:~/packages/cloud-installer/tools$ sudo apt-get autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  bridge-utils cloud-image-utils debootstrap distro-info euca2ools libboost-thread1.54.0 liblxc0
  librados2 librbd1 libseccomp2 lxc lxc-templates python-distro-info python-requestbuilder python3-lxc
  qemu-utils
0 upgraded, 0 newly installed, 16 to remove and 440 not upgraded.
After this operation, 12.9 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 174629 files and directories currently installed.)
Removing lxc-templates (1.0.0~rc3-0ubuntu1) ...
Removing lxc (1.0.0~rc3-0ubuntu1) ...
stop: Job failed while stopping
invoke-rc.d: initscript lxc-net, action "stop" failed.
dpkg: error processing package lxc (--remove):
 subprocess installed pre-removal script returned error exit status 1
lxc-net start/running
Removing cloud-image-utils (0.27-0ubuntu7) ...
Removing debootstrap (1.0.59) ...
Removing distro-info (0.12) ...
Removing euca2ools (3.0.2-1ubuntu1) ...
Removing qemu-utils (1.7.0+dfsg-3ubuntu2) ...
Removing librbd1 (0.72.2-1) ...
Removing librados2 (0.72.2-1) ...
Removing libboost-thread1.54.0:amd64 (1.54.0-4ubuntu3) ...
Removing python-distro-info (0.12) ...
Removing python-requestbuilder (0.1.0~beta2-1) ...
dpkg: python3-lxc: dependency problems, but removing anyway as you requested:
 lxc depends on python3-lxc.

Removing python3-lxc (1.0.0~rc3-0ubuntu1) ...
dpkg: liblxc0: dependency problems, but removing anyway as you requested:
 lxc depends on liblxc0 (= 1.0.0~rc3-0ubuntu1).

Removing liblxc0 (1.0.0~rc3-0ubuntu1) ...
Removing libseccomp2:amd64 (2.1.0+dfsg-1) ...
dpkg: bridge-utils: dependency problems, but removing anyway as you requested:
 lxc depends on bridge-utils.

Removing bridge-utils (1.5-6ubuntu2) ...
Processing triggers for man-db (2.6.6-1) ...
Processing triggers for libc-bin (2.18-0ubuntu6) ...
Errors were encountered while processing:
 lxc
E: Sub-process /usr/bin/dpkg returned an error code (1)

I'm not exactly sure what the problem is here, but autoremove should never break :-)

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Could you please show the contents of /var/log/upstart/lxc-net.log?

Changed in lxc (Ubuntu):
status: New → Incomplete
Revision history for this message
Tycho Andersen (tycho-s) wrote :

Hey, sorry about that, forgot to post:

CloudFive:~/packages/cloud-installer/tools 1$ sudo cat /var/log/upstart/lxc-net.log
iptables: Bad rule (does a matching rule exist in that chain?).

Revision history for this message
Stéphane Graber (stgraber) wrote :

What kernel are you running on?

The last time I saw that specific error, it was with a kernel not supporting mangle+fill-checksum.

Revision history for this message
Tycho Andersen (tycho-s) wrote : Re: [Bug 1281793] Re: lxc packaging w/ bridge-utils is confused

On Wed, Feb 19, 2014 at 03:53:47PM -0000, Stéphane Graber wrote:
> What kernel are you running on?
>
> The last time I saw that specific error, it was with a kernel not
> supporting mangle+fill-checksum.

CloudFive:~/packages/cloud-installer/tools$ uname -r
3.13.0-5-generic

Basically, a reasonably recent version of the stock trusty kernel. Is
there somewhere I can look specifically?

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Quoting Tycho Andersen (<email address hidden>):
> Hey, sorry about that, forgot to post:
>
> CloudFive:~/packages/cloud-installer/tools 1$ sudo cat /var/log/upstart/lxc-net.log
> iptables: Bad rule (does a matching rule exist in that chain?).

Do you happen to have ufw installed? Did you manually edit your
firewall at any point since the last boot before that failure?

In any case, it seems best to add '|| true' to the end of all the
iptables commands in the post-stop.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for lxc (Ubuntu) because there has been no activity for 60 days.]

Changed in lxc (Ubuntu):
status: Incomplete → Expired
Revision history for this message
JoaoCC (joaocc) wrote :

I have this same problem.
Ubuntu 14.04, lxc 1.0.3-0ubuntu3, shorewall 4.5.21.6-1
Basically "lxcbr0" doesn't start, and I get the following message at /var/log/upstart/lxc-net.log
    iptables: Bad rule (does a matching rule exist in that chain?).
Any ideas?
Thx

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Please open a new bug

Revision history for this message
Daniel Ghe (ghe-daniel) wrote :

On ubuntu 14.04, to remove lxc, first run:
service lxc-net stop
then
aptitude remove lxc

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.