I happened to realize that the failure changed since yesterday. The last two logs: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/l/livecd-rootfs/20190128_084254_b5919@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/l/livecd-rootfs/20190128_090339_25cc4@/log.gz
Point to a different issue being triggered now. The tail of the fails is now: + udevadm settle + '[' -n /dev/mapper/loop0p1 -a -b /dev/mapper/loop0p1 ']' + '[' -e /etc/mtab ']' + e2fsck -y -E discard /dev/mapper/loop0p1 e2fsck 1.44.5 (15-Dec-2018) /dev/mapper/loop0p1 is in use. e2fsck: Cannot continue, aborting. + clean_loops + local kpartx_ret + local kpartx_stdout + '[' -n binary/boot/disk.ext4 ']' + sync + kpartx_ret= ++ kpartx -v -d binary/boot/disk.ext4 + kpartx_stdout='loop0p1 is in use. Not removingloop deleted : /dev/loop0' + kpartx_ret=1 + echo 'loop0p1 is in use. Not removingloop deleted : /dev/loop0' loop0p1 is in use. Not removingloop deleted : /dev/loop0 + '[' -n 1 ']' + grep -q 'loop deleted' + echo 'loop0p1 is in use. Not removingloop deleted : /dev/loop0' + echo 'Suppressing kpartx returning error (#860894)' Suppressing kpartx returning error (#860894) + unset backing_img + '[' -z /dev/mapper/loop0p1 ']' + unset loop_device + unset loop_raw + unset rootfs_dev_mapper E: config/hooks/014-disk-image.binary failed (exit non-zero). You should check for errors. P: Begin unmounting filesystems... P: Saving caches... P: Begin unmounting filesystems... P: Saving caches... That matches what I see when running it in autopkgtest locally which means it might be debuggable after all. Unfortunately the test runs some cleanup stages that make the situation that made it fail disappear. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1813730 Title: livecd-rootfs autopkgtest fails configuring required packages calling out util-linux Status in livecd-rootfs package in Ubuntu: New Status in python-apt package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in rsync package in Ubuntu: Invalid Status in util-linux package in Ubuntu: New Status in xz-utils package in Ubuntu: Invalid Bug description: As of recently autopkgtests of livecd-rootfs fail. It seems unrelated to which package is tested, the failure is always the same. => http://autopkgtest.ubuntu.com/packages/l/livecd-rootfs/disco/amd64 It is failing for qemu, xz-utils, rsync, python-apt and qemu. From the log we see all sub-cases fail with a tail like: W: Failure while configuring required packages. W: See /tmp/tmp.qy1mya9uZ0/ubuntu-base::/chroot/debootstrap/debootstrap.log for details (possibly the package util-linux is at fault) P: Begin unmounting filesystems... P: Saving caches... P: Begin unmounting filesystems... P: Saving caches... autopkgtest [13:39:10]: test default-bootstraps: -----------------------] default-bootstraps FAIL non-zero exit status 1 Full log of one such cases: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco/disco/amd64/l/livecd- rootfs/20190125_133950_dc236@/log.gz I found no related open bugs in https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bugs?orderby=-date_last_updated&start=0 nor in https://bugs.launchpad.net/ubuntu/+source/util-linux/+bugs?orderby=-date_last_updated&start=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1813730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
