Comment 6 for bug 1716992

Revision history for this message
Robert C Jennings (rcj) wrote :

Marking xenial as verification failed. I have been able to test on xenial and it failed quickly.

Our first call to 'udevadm settle' in our first binary hook fails:
+ teardown_mountpoint binary/boot/filesystem.dir
+ local mountpoint=binary/boot/filesystem.dir
+ umount binary/boot/filesystem.dir/var/cache/apt
+ umount binary/boot/filesystem.dir/var/lib/apt
+ umount binary/boot/filesystem.dir/tmp
+ umount binary/boot/filesystem.dir/sys
+ umount binary/boot/filesystem.dir/proc
+ umount -R binary/boot/filesystem.dir/dev
+ udevadm settle
config/functions: line 107: udevadm: command not found
E: config/hooks/030-root-tarball.binary failed (exit non-zero). You should check for errors.

In a prior good build we see that we had not been calling udevadm until after the first call to mount_image in the common functions. We were getting udev installed as a side-effect of a call to install kpartx:
+ mount_image binary/boot/disk.ext4 1
+ apt-get install -qqy kpartx
Selecting previously unselected package udev.

I have a possible fix @ http://bazaar.launchpad.net/~rcj/livecd-rootfs/xenial-proposed/revision/1420 but I'm unable to test before I'm out of the office (and the builders have a spectacular backlog currently of ~9hrs).