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

[Dan Watkins]

This change will be backported to xenial, but only once we've heard that
we've actually fixed it.

Robert, GGeorg, LoOoD, does the box I provided fix the issue?

(Also, Robert, I really do understand the frustration but this wasn't
actually as simple a fix as you seem to think; Vagrant boxes should have
their hostname set dynamically at boot, which means you can't simply
write out the hostname to /etc/hosts during the image build process.
And when you add in to this the fact that a lot of behaviour that is
clearly expected of Vagrant boxes isn't actually documented anywhere[0],
any fix becomes time-consuming as you have to try and work out what the
expected behaviour is by looking at other Vagrant boxes.)


[0] Search for "host" in https://www.vagrantup.com/docs/boxes/base.html

-- 
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