livecd-rootfs fails in lxd container because mounts under /dev are not unmounted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
livecd-rootfs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Zesty |
Fix Released
|
Undecided
|
Unassigned |
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.
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.
description: | updated |
fixed in livecd-rootfs 2.453, currently in artful-proposed.