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

GGeorg georg-ubuntu.com at glas.eu.org
Mon May 9 09:29:36 UTC 2016

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"

** Package changed: ubuntu => livecd-rootfs (Ubuntu)

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.

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

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

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

More information about the foundations-bugs mailing list