Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Ubuntu22: MonitorHostname does not update iDNS #2999

Open
ryanhamel opened this issue Dec 21, 2023 · 0 comments
Open

[BUG] Ubuntu22: MonitorHostname does not update iDNS #2999

ryanhamel opened this issue Dec 21, 2023 · 0 comments
Assignees

Comments

@ryanhamel
Copy link

OS: Ubuntu 22 HPC image (microsoft-dsvm:ubuntu-hpc:2204:22.04.2023111801) though likely any Ubuntu 22 image will cause this.
waagent --version
WALinuxAgent-2.9.0.4 running on ubuntu 22.04
Python: 3.10.12
Goal state agent: 2.9.1.1

VMs that change their hostname are not registering their hostname in Azure internal DNS. The logs show that the hostname change is detected, and then that eth0 link is set down and then up, however using nslookup the DNS entry is never actually updated. So WALA seems to be doing everything it intends to do, but the result is that internal DNS is never updated. Ubuntu 20 and Almalinux 8 worked without issue in the same cluster.

  1. There is no error in the log, it is a silent bug. Setting eth0 down and up again does not cause dhcp to renew the hostname.
  2. Serial console output is irrelevant here.
  3. To reproduce, start an Ubuntu 22 HPC VM, run hostnamectl set-hostname SOME_TEMPORARY_HOSTNAME, wait a few minutes and run nslookup IP_ADDRESS.

As a mitigation for our users (Azure CycleCloud with Slurm), we are telling our customers to run systemctl restart systemd-networkd, which causes the hostname to be registered in internal DNS. This seems to be the behaviour that WALA does on Ubuntu 20, after reading through the source code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants