Can confirm I am also running into this. It's preventing vagrant configurations that involve private networking from loading as this error stops the provisioning process- basically making it impossible to use these images for testing certain (fairly common) scenarios using vagrant.
If there's a reason to keep the hostname out of /etc/hosts then disabling DNS in sudo and ssh should resolve some of the issues. -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
