This bug is believed to be fixed in cloud-init in 18.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 Ubu
This bug was fixed in the package cloud-init - 17.2-9-gdf24daa8-0ubuntu1
---
cloud-init (17.2-9-gdf24daa8-0ubuntu1) bionic; urgency=medium
* New upstream snapshot.
- tests: update apt sources list test [Joshua Powers]
- tests: clean up image properties [Joshua Powers]
-
** Changed in: cloud-init
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722668
Title:
Azure: bouncing of network device/publishing of hostname fails on
a
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/335470
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722668
Title:
Azure: bouncing of network
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/335465
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722668
Title:
Azure: bouncing of network
I linked a couple other bugs here.
What I think we should do is have local datasources set the hostname (`hostname
`) and update the system's config (write to /etc/hostname) at local time
frame once per instance.
Then, on that first instance boot, the dhcp would occur with the cloud-
provider pr
Note that bug 1722668 in cloud-init means there is still work to do
after this bug is fixed. hostnames wont be "published" correctly, but
this bug is more severe. We'll work the other in parallel.
** Changed in: cloud-init (Ubuntu)
Importance: Medium => Critical
** Changed in: cloud-init (Ub
