This script shows the failure, downloading a xenial cloud-image that has vmlinuz-4.4.0-53-generic (release-20161214) and one that has vmlinuz-4.4.0-57-generic (release-20161221).
Other differences are changed: ['linux-image-virtual', 'apport', 'systemd', 'linux-image-4.4.0-57-generic', 'cloud-init', 'python3-apport', 'libpam-systemd:amd64', 'initramfs-tools-bin', 'linux-headers-virtual', 'isc-dhcp-client', 'grub-legacy-ec2', 'isc-dhcp-common', 'linux-virtual', 'open-iscsi', 'cloud-initramfs-dyn-netconf', 'initramfs-tools', 'initramfs-tools-core', 'libsystemd0:amd64', 'libudev1:amd64', 'udev', 'systemd-sysv', 'cloud-initramfs-copymods', 'overlayroot', 'python3-problem-report', 'ifupdown', 'linux-headers-generic'] I'll check if just the kernel upgrade changes things now. I also suspect udev. ** Attachment added: "go-reproduce: download xenial images, show how to reproduce failure" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651602/+attachment/4795375/+files/go-reproduce.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651602 Title: [2.1.1] Yakkety - MAAS has nvme0n1 set as boot disk, curtin fails To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1651602/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
