Fix confirmed. Here's how I tested:
- Downloaded current xenial vagrant box and started a VM from it - Enabled xenial-proposed repository - Installed livecd-rootfs from -proposed, version 2.408.3 - ran the following commands... sudo -i mkdir /build cd /build cp -a /usr/share/livecd-rootfs/live-build/auto . export SUITE=xenial export ARCH=amd64 export PROJECT=ubuntu-cpc export MIRROR=http://archive.ubuntu.com/ubuntu/ lb config cd config/hooks rm 031-root-xz.binary 033-disk-image-uefi.binary 034-disk-image-ppc64el.binary 040-qcow2-image.binary 040-vmdk-image.binary 041-vmdk-ova-image.binary 032-root-squashfs.binary lb build - Copied the created vagrant box from /build/livecd.ubuntu-cpc.vagrant.box to my host and launched a new VM from it - Checked that new VM had randomized name and that default synced folder was mounted. Also checked that sudo did not complain about hostname resolution. Looks good to me! ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561250 Title: Xenial vagrant image is missing its hostname in /etc/hosts To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1561250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
