[Bug 1573015] Re: xenial cloudimage with missing hostname on hosts

[Paul White]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.

Do you still see a problem related to the one that you reported when
using a currently supported version of Ubuntu? Please let us know if you
do otherwise this report can be left to expire in approximately 60 days
time.


** Changed in: hundredpapercuts
       Status: Confirmed => Incomplete

** Changed in: hostname (Ubuntu)
       Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to hostname in Ubuntu.
https://bugs.launchpad.net/bugs/1573015

Title:
  xenial cloudimage with missing hostname on hosts

Status in One Hundred Papercuts:
  Incomplete
Status in hostname package in Ubuntu:
  Incomplete

Bug description:
  Install Vagrant / Virtualbox

  On Terminal run:

  $> vagrant init

  Edit the Vagrantfile to change the box name from "base" to
  "ubuntu/xenial64"

  Then on the terminal again do:

  $> vagrant up

  After installing do:

  $> vagrant ssh

  $> sudo su

  You will get a message stating: "sudo: unable to resolve host ubuntu-
  xenial"

  The reason for this message is because the entry on /etc/hostname
  (which have "ubuntu-xenial") doesn't exist on /etc/hosts

  To Fix:

  Edit the /etc/hosts:

  $> sudo vim /etc/hosts (for instance)

  And on the entry:

  127.0.0.1 localhost

  Change to:

  127.0.0.1 localhost ubuntu-xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1573015/+subscriptions