This has been verified using 2.408.58 in xenial-proposed. I have built the qcow2 image target of the ubuntu-cpc project with and without a cohort key.
I added the following to the qcow2 binary hook: . /build/config/binary mkdir qcowmp mount_disk_image binary/boot/disk-uefi.ext4 qcowmp snap_preseed qcowmp/ lxd umount_disk_image qcowmp rmdir qcowmp Booting the resulting livecd.ubuntu-cpc.uefi1.img which came out of the builds with/without the snap cohort key shows that both boot and 'systemctl is-system-running' gets to 'running' (no failed units). The output of 'snap list' shows lxd and core as expected and 'snap info --verbose' run against each of the snaps in either image confirms that the cohort key did not persist into the resulting image as expected. Based on this testing I will mark the bug as verification-done. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866159 Title: SRU: Use a snap cohort key for consistent parallel builds in Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1866159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
