Hostname not added to /etc/hosts on CentOS 7.0

[biemond]

Hi,

I am using vagrant 1.6.5 and this fixed some of my CentOS 7.0 issues.
It sets the hostname ( I checked with uname -a ) and also my private network device is created.

but my /etc/hosts file is not updated with the FQDN, in CentOS6.5 this works perfectly

 [root@admin ~]# cat /etc/hosts  
 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
  ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

Vagrantfile

admin.vm.hostname = "admin.example.com"
admin.vm.network :private_network, ip: "10.10.10.10"

Thanks

[andytson]

It was incorrectly assumed in #4352 that hostnamectl set-hostname would set everything that the pre-centos/rhel 7.0 process previously did

1. Update sysconfig
2. Update hostname via sudo hostname
3. Update /etc/hosts
4. Update DHCP_HOSTNAME in /etc/sysconfig[/network-scripts/ifcfg-*]
5. Restart networking.

I believe what was the equivalent to 1 and 2 is definitely done by hostnamectl (its set for the current session and is still there on restart), I'm unsure of whether 4 (and therefore 5) is needed, but 3. Update /etc/hosts definitely isn't done by hostnamectl

[mitchellh]

This is the reason I asked but it looks like I got the wrong answer. Got it.

[mitchellh]

Thanks for the report!

[Xylakant]

I was trying to take a stab at fixing this, but alas, since I use the vmware fusion plugin I failed after jumping through a long series of hoops since the plugin does not work with development versions of vagrant.

[andytson]

I think there's some inconsistency in the usage of the DHCP hostname across guests. Only the redhat < 7 and the pId guests appear to set this, which is either that the other guests magically set this automatically, or the people who provided the PRs only considered their choice distribution for the features

[Xylakant]

I must admit I never used DHCP to configure the private/public network adapters, so I have no test setup. According to some info setting DHCP_HOSTNAME is not required when NetworkManager is used, but the RHEL documentation is pretty thin on that issue. It's be easy to adapt the PR, though.