[Bug 1573015] [NEW] xenial cloudimage with missing hostname on hosts

Luis Ferro lferro9000 at gmail.com
Thu Apr 21 12:42:03 UTC 2016


Public bug reported:

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

** Affects: hostname (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: cloud hostname xenial

-- 
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 hostname package in Ubuntu:
  New

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/ubuntu/+source/hostname/+bug/1573015/+subscriptions



More information about the foundations-bugs mailing list