[Bug 1561250] Re: Xenial vagrant image is missing its hostname in /etc/hosts
christophe
christophe.bornet at free.fr
Wed May 11 13:23:51 UTC 2016
On trusty, the hostname was not in /etc/hosts and it was working fine.
The real issue here is that sudo looks into DNS before hostname.
In /etc/nsswitch.conf, we had on trusty:
hosts: files myhostname mdns4_minimal [NOTFOUND=return] dns
We now have:
hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname
--
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
More information about the foundations-bugs
mailing list