Public bug reported:
Tested with latest Ubuntu 14.04 image on Azure (20150908).
In Azure, the DHCP client on Ubuntu VMs is configured to push the
current hostname to the DHCP server, which then publishes the hostname
into Azure DNS. However, after changing the hostname and rebooting, the
old hostname is always pushed to Azure DNS instead of the new one.
Repro steps:
- Create Ubuntu 14.04 VM on Azure
- Edit /etc/hostname to change the hostname
- Reboot the VM
- After reboot, the hostname will be changed, but commands like 'hostname -f'
and 'sudo' will complain that the new hostname cannot be found via a DNS lookup.
Next, bounce DHCP to force the DNS update and check that the new
hostname has been published:
- Run "sudo ifdown eth0 && sudo ifup eth0"
- After a few seconds run: "host NEWHOSTNAME".
DNS lookup to the new hostname should succeed now indicating that the
new hostname was pushed to the DHCP server and into Azure DNS. Commands
like 'hostname -f' and 'sudo' will work now.
However, after rebooting the OLD hostname will again be published to
DNS:
- Run 'sudo reboot'
- After logging in, run "host OLDHOSTNAME" and see that the old hostname is
again published to DNS. Commands like "hostname -f" and "host NEWHOSTNAME"
will again fail.
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1498179
Title:
Azure: After changing hostname, old hostname is still published to
DHCP after reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1498179/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
