group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1716465@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package livecd-rootfs - 2.441.5

---------------
livecd-rootfs (2.441.5) zesty; urgency=medium

  [ Colin Watson ]
  * Mount and unmount /dev recursively, to cope with setups where there are
    interesting bind-mounts under /dev (e.g. loop devices bind-mounted by
    LXD).  LP: #1716465.

  [ Balint Reczey ]
  * Fix suppression of kpartx error.  LP: #1684090.

 -- Steve Langasek <steve.langasek@xxxxxxxxxx>  Mon, 11 Sep 2017
11:59:59 -0700

** Changed in: livecd-rootfs (Ubuntu Zesty)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1716465

Title:
  livecd-rootfs fails in lxd container because mounts under /dev are not
  unmounted

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Zesty:
  Fix Released

Bug description:
  [SRU Justification]
  After the move of livefs builds to lxd containers, cloud image builds will fail because loop devices are separate mount points set up by lxd and are not getting bind mounted correctly into the livecd-rootfs chroot, therefore they are not present at the right point for kpartx -d to run to free the devices.

  This is fixed by mount --rbind of /dev instead of mount --bind, which
  then also requires changes for the unwinding.

  [Test case]
  Daily images on cloud-images.ubuntu.com are currently failing to build as a result of this bug.  The daily images are built using a private overlay on top of the livecd-rootfs in the archive, so unfortunately we can't describe directly a public end-to-end test case for this.

  We will verify this fix by verifying that we are able to produce daily
  cloud images again for each of the releases.

  [Regression potential]
  For xenial we should also verify this change by doing a test build of all images against xenial-proposed to guard against any possible regressions.
  For zesty, there are no ongoing builds of any projects other than cloud images so there is no risk of external regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1716465/+subscriptions