group.of.nepali.translators team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

This bug is believed to be fixed in cloud-init in 17.1. If this is still
a problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: cloud-init
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1674685

Title:
  hostname ddns update is not done on azure with built-in agent path.

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  The network device on Azure is configured via dhcp.  DNS records are
  updated for the host with the dhcp's request (dyndns).

  Cloud-init has two operation modes on Azure.
  a.) builtin: cloud-init does negotiation with the "fabric" (cloud platform)
      directly.
  b.) interaction with walinux-agent: cloud-init invokes walinux-agent
      and expects it to do negotiation.

  The system's hostname is provided to cloud-init via info on a cdrom.
  cloud-init reads that hostname and then updates the system's hostname.
  When configured to use walinux-agent, cloud-init would then bounce
  the network device to publish this hostname change.

  The bug here was that this did not happen in the builtin path, and
  as a result systems would not have dns updated for their hostname.

  This is not a problem for xenial or yakkety as they use the
  walinuxagent path.

  [Test Case]
  To verify no regression
  start an instance on azure
  enable proposed, update, upgrade
  rm -Rf /var/lib/cloud /var/log/cloud-init*
  reboot

  [Regression Potential]
  Regression risk is very low since this code path is not used in 16.04 or
  16.10.  The changed code path is only used in 17.04+.  Thus the test case
  listed above is simple instance boot.

  [Other Info]
  Upstream commit:
   https://git.launchpad.net/cloud-init/commit/?id=86715c88aab8561

  === End SRU Template ===

  Brent Baude and Paul Meyer realized that on Azure, that when the
  'agent_command' is set to __builtin__ (the current default in trunk)
  that cloud-init does not bounce the network device in order to do a
  ddns update of the systems' hostname.

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