-
Notifications
You must be signed in to change notification settings - Fork 840
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
hostname ddns update is not done on azure with built-in agent path. #2833
Comments
Launchpad user Launchpad Janitor(janitor) wrote on 2017-03-26T08:03:00.706850+00:00 This bug was fixed in the package cloud-init - 0.7.9-77-g4a2b2f87-0ubuntu1 cloud-init (0.7.9-77-g4a2b2f87-0ubuntu1) zesty; urgency=medium
-- Scott Moser smoser@ubuntu.com Fri, 24 Mar 2017 16:50:56 -0400 |
Launchpad user Brian Murray(brian-murray) wrote on 2017-04-10T22:25:14.803631+00:00 Hello Scott, or anyone else affected, Accepted cloud-init into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-90-g61eb03fe-0ubuntu1~16.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! |
Launchpad user Brian Murray(brian-murray) wrote on 2017-04-10T22:47:36.842885+00:00 Hello Scott, or anyone else affected, Accepted cloud-init into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-90-g61eb03fe-0ubuntu1~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! |
Launchpad user Scott Moser(smoser) wrote on 2017-04-13T21:05:26.145536+00:00 launch an instance on azure of yakkety and of xenial$ azure vm create --vm-size=Basic_A0 $ azure vm create --vm-size=Basic_A0 on each system% git clone https://git.launchpad.net/~smoser/cloud-init/+git/sru-info this just sets the hostname back to the stock 'ubuntu'so the code will think it needs to re-publish itas it only publishes if it differs from the existing.% echo "ubuntu" | sudo tee /etc/hostname reconnect and verify yakkety$ cat /etc/cloud/build.info $ dpkg-query --show cloud-init $ lsb_release -sc $ grep WARN /var/log/cloud-init.log || echo no warn $ cat /run/cloud-init/result.json reconnect and verify xenial$ dpkg-query --show cloud-init |
Launchpad user Launchpad Janitor(janitor) wrote on 2017-04-20T19:33:34.017361+00:00 This bug was fixed in the package cloud-init - 0.7.9-90-g61eb03fe-0ubuntu1~16.10.1 cloud-init (0.7.9-90-g61eb03fe-0ubuntu1~16.10.1) yakkety; urgency=medium
-- Scott Moser smoser@ubuntu.com Mon, 03 Apr 2017 12:03:30 -0400 |
Launchpad user Steve Langasek(vorlon) wrote on 2017-04-20T19:34:55.707640+00:00 The verification of the Stable Release Update for cloud-init has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. |
Launchpad user Launchpad Janitor(janitor) wrote on 2017-04-20T19:35:54.384643+00:00 This bug was fixed in the package cloud-init - 0.7.9-90-g61eb03fe-0ubuntu1~16.04.1 cloud-init (0.7.9-90-g61eb03fe-0ubuntu1~16.04.1) xenial-proposed; urgency=medium
-- Scott Moser smoser@ubuntu.com Mon, 03 Apr 2017 11:52:56 -0400 |
Launchpad user Scott Moser(smoser) wrote on 2017-09-23T02:30:06.035388+00:00 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. |
This bug was originally filed in Launchpad as LP: #1674685
Launchpad details
Launchpad user Scott Moser(smoser) wrote on 2017-03-21T13:36:07.512640+00:00
=== 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.
The text was updated successfully, but these errors were encountered: