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

[j bennett]

Based on #13 and related comments, I noticed that on my AWS account I
wasn't getting a Public DNS assigned  each time I launched ami-08490c68.

Found this link to resolve that by adding a Virtual Private Cloud (VPC)
per this link:

http://stackoverflow.com/questions/20941704/ec2-instance-has-no-public-
dns

Adding the VPC seemed to have fixed the Public DNS issue and the "unable
to resolve host" issue on my running instance and a new one as the
Public DNS is showing up now.

Not a fix, but seems like it is a work around for my AWS based stuff and
clarified a bit some of the other comments on this thread above for me.

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