yahoo-eng-team team mailing list archive

[Paul Meyer <paul.meyer@xxxxxxxxxxxxx>]

Public bug reported:

Verified on Azure, using Trusty
(Canonical:UbuntuServer:14.04.5-LTS:14.04.201803080) (cloud-init
0.7.5-0ubuntu1.22)

1. create a Trusty VM:
   az vm create -g paulmey-test -n ubuntu14 --image Canonical:UbuntuServer:14.04.5-LTS:latest
2. On the VM, edit /etc/waagent.conf to set Provisioning.MonitorHostName=y and restart the agent.
   This sets waagent to ifdown/ifup when it detects a hostname change such that the new hostname is
   sent on the DHCP request, which in Azure populates the instance DNS.
3. verify 'nslookup ubuntu14' shows a DNS record for the initial hostname (ubuntu14)
4. run 'hostnamectl set-hostname seeifitsticks' to change the hostname
5. Wait a minute for the update to propagate, verify that 'nslookup seeifitsticks' now shows a DNS
   record for the new hostname. Verify that /etc/hostname is updated. Verify that 'nslookup ubuntu14'
   no longer returns a valid DNS record.
6. reboot the vm
7. Once back up, notice that the hostname is seeifitsticks. However, 'nslookup seeifitsticks' returns
   NXDOMAIN, which 'nslookup ubuntu14' shows a DNS record.

>From the cloud-init log, it looks like cloud-init sets the hostname to
whatever is in the ovf-env.xml during interface bounce. On Xenial, the
data source is loaded from cache, which is why this code does not even
run.

** Affects: cloud-init
     Importance: Undecided
         Status: New

** Attachment added: "repro cloud-init log"
   https://bugs.launchpad.net/bugs/1755260/+attachment/5077320/+files/cloud-init.log

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1755260

Title:
  [Azure] Published hostname (ddns) gets reset on reboot after
  `hostnamectl set-hostname`

Status in cloud-init:
  New

Bug description:
  Verified on Azure, using Trusty
  (Canonical:UbuntuServer:14.04.5-LTS:14.04.201803080) (cloud-init
  0.7.5-0ubuntu1.22)

  1. create a Trusty VM:
     az vm create -g paulmey-test -n ubuntu14 --image Canonical:UbuntuServer:14.04.5-LTS:latest
  2. On the VM, edit /etc/waagent.conf to set Provisioning.MonitorHostName=y and restart the agent.
     This sets waagent to ifdown/ifup when it detects a hostname change such that the new hostname is
     sent on the DHCP request, which in Azure populates the instance DNS.
  3. verify 'nslookup ubuntu14' shows a DNS record for the initial hostname (ubuntu14)
  4. run 'hostnamectl set-hostname seeifitsticks' to change the hostname
  5. Wait a minute for the update to propagate, verify that 'nslookup seeifitsticks' now shows a DNS
     record for the new hostname. Verify that /etc/hostname is updated. Verify that 'nslookup ubuntu14'
     no longer returns a valid DNS record.
  6. reboot the vm
  7. Once back up, notice that the hostname is seeifitsticks. However, 'nslookup seeifitsticks' returns
     NXDOMAIN, which 'nslookup ubuntu14' shows a DNS record.

  From the cloud-init log, it looks like cloud-init sets the hostname to
  whatever is in the ovf-env.xml during interface bounce. On Xenial, the
  data source is loaded from cache, which is why this code does not even
  run.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1755260/+subscriptions