** Description changed: - 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. + [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.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716465 Title: livecd-rootfs fails in lxd container because mounts under /dev are not unmounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1716465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
