[Bug 1561250] Re: Xenial vagrant image is missing its hostname in /etc/hosts
Presumably they'll stick to the "S" in LTS and backport this change, but I can understand their desire to test it quickly before diving in. I also understand limited resources. However, I think a reprioritization is in order here. This bug was not a difficult or time consuming one to solve. Further, in order for people to use Ubuntu in production environments they have to use them in test environments. Vagrant allows us to do this easily, and for people developing software or looking at upgrading infrastructure and looking to test compatibility it's really nice to have a quick to use (and free) server that we can test on. This bug has actually stopped my company from upgrading our main infrastructure to the latest LTS because of our use of vagrant for testing and development. -- 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
[Bug 1561250] Re: Xenial vagrant image is missing its hostname in /etc/hosts
This bug- which literally just required a line in the hosts file- is still not resolved months later. Does the cloud team just not want people to upgrade to the latest LTS version? I can't imagine any other reason to ignore this issue, especially considering it's easy fix. -- 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
[Bug 1561250] Re: Xenial vagrant image is missing its hostname in /etc/hosts
There is a really amazingly simple work around to this problem that works without needing a custom box. In your VagrantFile use the config.vm.hostname option to specify a hostname- config.vm.hostname = "vagrant" That will change the hostname before the networking and provisioning steps occur (I'm not sure how, but I did confirm this was true) and allow you to set the custom options you'd like. -- 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
[Bug 1561250] Re: Xenial vagrant image is missing its hostname in /etc/hosts
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
