** Changed in: cloud-init (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Yakkety)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Yakkety)
Importance: Undecided => Medium
** Description changed:
- 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.
+ === Begin SRU Template ===
+ [Impact]
+ When configured to use the 'builtin' agent rather than interacting
+ with walinuxagent, cloud-init would not bounce the network config.
+ The result was that hostname updates would from the guest were not
+ published to Azure fabric.
+
+ This is not a problem for xenial or yakkety as they use the
+ walinuxagent path.
+
+ [Test Case]
+ To verify no regresion
+ start an instance on azure
+ enable proposed, update, upgrade
+ rm -Rf /var/lib/cloud /var/log/cloud-init*
+ reboot
+
+ [Regression Potential]
+ low.
+
+ [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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674685
Title:
hostname ddns update is not done on azure with built-in agent path.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1674685/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
