Closed ubuntu-server-builder closed 1 year ago
Launchpad user Scott Moser(smoser) wrote on 2016-12-23T17:34:08.010256+00:00
This is fixed in cloud-init 0.7.9.
Launchpad user Brian Murray(brian-murray) wrote on 2017-02-06T15:44:37.775888+00:00
Hello Lars, 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-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 Brian Murray(brian-murray) wrote on 2017-02-06T21:33:34.171887+00:00
Hello Lars, 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-0ubuntu1~16.04.2 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 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-02-09T02:40:22.098295+00:00
I'm marking this bug fixed by nature of correct xenial boot on openstack and lxd. The bug was opened on another distro and related to a path that is not common in cloud-init on ubuntu.
The fix seems straight forward enough.
https://code.launchpad.net/~larsks/cloud-init/+git/cloud-init/+merge/312612
I'm not happy with lack of positive validation of the fix, but that is all we have.
Launchpad user Łukasz Zemczak(sil2100) wrote on 2017-02-09T18:02:09.964863+00:00
Hello Lars, 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-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 Scott Moser(smoser) wrote on 2017-02-10T13:00:56.617800+00:00
16.10/Yakkety:
I'm marking this bug fixed by nature of correct xenial boot on openstack and | lxd. The bug was opened on another distro and related to a path that is not | common in cloud-init on ubuntu. |
---|---|---|
The fix seems straight forward enough. | ||
https://code.launchpad.net/~larsks/cloud-init/+git/cloud-init/+merge/312612 | ||
I'm not happy with lack of positive validation of the fix, but that is all | ||
we have. |
Scott
Launchpad user Launchpad Janitor(janitor) wrote on 2017-02-22T00:42:21.799794+00:00
This bug was fixed in the package cloud-init - 0.7.9-0ubuntu1~16.10.1
cloud-init (0.7.9-0ubuntu1~16.10.1) yakkety; urgency=medium
New upstream release.
-- Scott Moser smoser@ubuntu.com Tue, 31 Jan 2017 21:02:28 -0500
Launchpad user Chris Halse Rogers(raof) wrote on 2017-02-22T00:42:44.316679+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-02-22T00:43:01.813488+00:00
This bug was fixed in the package cloud-init - 0.7.9-0ubuntu1~16.04.2
cloud-init (0.7.9-0ubuntu1~16.04.2) xenial-proposed; urgency=medium
cloud-init (0.7.9-0ubuntu1~16.04.1) xenial-proposed; urgency=medium
New upstream release.
-- Scott Moser smoser@ubuntu.com Mon, 06 Feb 2017 16:18:28 -0500
This bug was originally filed in Launchpad as LP: #1647910
Launchpad details
Launchpad user Lars Kellogg-Stedman(larsks) wrote on 2016-12-07T02:11:42.837466+00:00
If no data source is available and the local hostname is set to "localhost.localdomain", and /etc/hosts looks like:
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
Then in sources/init.py in get_hostname:
And ultimately the system hostname will be set to 'localhost.localdomain.localdomain', which isn't useful to anybody.
Also reported in:
https://bugzilla.redhat.com/show_bug.cgi?id=1389048