Public bug reported: We have been having very frequent image build failures in the livecd- rootfs autopkgtests, due to a 'debugging output' invocation of blkid. It's not clear when these started - they started before the merge of the new version of util-linux, so it doesn't appear to be a blkid regression - but they definitely seem to now be more frequent, and to happen more often on ppc64el than on amd64. (amd64 runs more image build tests in autopkgtest than other archs, so it may affect that arch more often despite not happening with greater frequency.)
One possibility is that this is a regression due to wrong behavior of losetup -P returning from the kernel before the devices are settled. If so, this must be a regression in the kernel or systemd since it doesn't line up with the change in util-linux. Since this blkid invocation is for debugging purposes anyway, we shouldn't fail the image build on it regardless of the cause. ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Package changed: util-linux (Ubuntu) => livecd-rootfs (Ubuntu) ** Summary changed: - after util-linux upgrade, blkid frequently exits non-zero in image builds + blkid frequently exits non-zero in image builds -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2034299 Title: blkid frequently exits non-zero in image builds Status in livecd-rootfs package in Ubuntu: New Bug description: We have been having very frequent image build failures in the livecd- rootfs autopkgtests, due to a 'debugging output' invocation of blkid. It's not clear when these started - they started before the merge of the new version of util-linux, so it doesn't appear to be a blkid regression - but they definitely seem to now be more frequent, and to happen more often on ppc64el than on amd64. (amd64 runs more image build tests in autopkgtest than other archs, so it may affect that arch more often despite not happening with greater frequency.) One possibility is that this is a regression due to wrong behavior of losetup -P returning from the kernel before the devices are settled. If so, this must be a regression in the kernel or systemd since it doesn't line up with the change in util-linux. Since this blkid invocation is for debugging purposes anyway, we shouldn't fail the image build on it regardless of the cause. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2034299/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp