[Bug 1561250] Re: Xenial vagrant image is missing its hostname in /etc/hosts

[Robert Hafner]

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
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1561250

Title:
  Xenial vagrant image is missing its hostname in /etc/hosts

Status in cloud-images:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed

Bug description:
  The vagrant build for xenial is missing an in /etc/hosts. This
  generates an error when running sudo.

  ubuntu at ubuntu-xenial:~$ cat /etc/hosts
  127.0.0.1 localhost

  # The following lines are desirable for IPv6 capable hosts
  ::1 ip6-localhost ip6-loopback
  fe00::0 ip6-localnet
  ff00::0 ip6-mcastprefix
  ff02::1 ip6-allnodes
  ff02::2 ip6-allrouters
  ff02::3 ip6-allhosts
  ubuntu at ubuntu-xenial:~$ sudo echo see the error ^^^^
  sudo: unable to resolve host ubuntu-xenial
  see the error ^^^^
  ubuntu at ubuntu-xenial:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1561250/+subscriptions