touch-packages team mailing list archive

[Robie Basak <1527666@xxxxxxxxxxxxxxxxxx>]

Correction. Rather than systemd being upgraded, I think there's
something that fires a trigger in it that sets off the failure.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1527666

Title:
  lxc on Wily cannot dist-upgrade Xenial

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Wily:
  Confirmed

Bug description:
  This affects 1.1.5-0ubuntu0.15.10.3 on Wily. I believe it also affects
  1.1.5-0ubuntu0.15.04.3 on Vivid.

  Downgrading to 1.1.4-0ubuntu1 fixes it, so it does not affect
  1.1.4-0ubuntu1 on Wily.

  My failure case is that I am running adt-run --apt-pocket=proposed -U
  with adt-virt-lxc and a test needs to upgrade systemd in the container
  which fails in the postinst. I think this comes down to lxc being
  unable to dist-upgrade xenial-proposed.

  I created the container with: sudo lxc-create -n xenial -t ubuntu-
  cloud -- -r xenial -T http://cloud-images.ubuntu.com/xenial/current
  /xenial-server-cloudimg-amd64-root.tar.gz -F

  Reproduce with: adt-run -U --apt-pocket=proposed libapache2-mod-perl2
  --- adt-virt-lxc -es xenial

  Expected: test pass (or fail for unrelated reason)

  Actual: test fail due to:

  Processing triggers for systemd (228-2ubuntu2) ...
  Failed to execute operation: Failed to activate service 'org.freedesktop.systemd1': timed out
  dpkg: error processing package systemd (--unpack):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for ufw (0.34-2) ...
  Errors were encountered while processing:
   systemd
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  blame: libapache2-mod-perl2
  badpkg: failed to run apt-get to satisfy adt-satdep.deb dependencies
  adt-run [15:57:15]: ERROR: erroneous package: failed to run apt-get to satisfy adt-satdep.deb dependencies

  I tried to reduce the failure case but I'm not sure how to manually
  activate a trigger for systemd.

  Workaround: downgrade using: sudo apt-get install lxc=1.1.4-0ubuntu1
  lxcfs=0.10-0ubuntu2 liblxc1=1.1.4-0ubuntu1 python3-lxc=1.1.4-0ubuntu1

  Presumably the failure case will stop working once systemd lands in
  the xenial release pocket, but perhaps reconfiguring it would still
  reproduce?

  Confirmed since pitti has experienced this as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1527666/+subscriptions