as far as i could see the problem is within the package live-build which is used to build the cloud-images
There is a hook for vagrant. i assume this is rather bogus, the hostname should not be something that changes per relesase, its better to have some solid default like "localhost" that is resolveable using /etc/hosts without any additional component. This will fix the issue for vagrant cloud images without breaking other images. ** Patch added: "live-build.patch" https://bugs.launchpad.net/ubuntu/+bug/1561250/+attachment/4659072/+files/live-build.patch ** Package changed: ubuntu => livecd-rootfs (Ubuntu) -- 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
