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

[Dan Watkins]

So I have just looked in to this, and I can't reproduce it.  I did the
following:

$ vagrant --version
Vagrant 1.8.1
$ vagrant init ubuntu/xenial64
<snip>
$ vagrant up
<snip>
$ vagrant ssh -- sudo grep hosts /etc/nsswitch.conf
hosts:          files dns

(I've also done some interactive sudo'ing in there, and I haven't seen
any issues)

I've done this with both the default hostname, and setting a hostname in
the Vagrantfile.

If someone can provide full reproduction steps, I'd be more than happy
to reopen this and address it, but as of now I can't find a bug to fix.
:)

** Changed in: cloud-images
       Status: Confirmed => Incomplete

** Changed in: livecd-rootfs (Ubuntu)
       Status: Confirmed => Incomplete

-- 
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:
  Incomplete
Status in livecd-rootfs package in Ubuntu:
  Incomplete

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