[Bug 1647910] Re: hostname is set incorrectly if localhostname is fully qualified

2017-02-21 Thread Launchpad Bug Tracker
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 * debian/update-grub-legacy-ec2: fix shell syntax error. (LP: #1662221) cloud-init (0.7.9-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

[Bug 1647910] Re: hostname is set incorrectly if localhostname is fully qualified

2017-02-21 Thread Launchpad Bug Tracker
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 * debian/copyright: update License field to include Apache-2.0 * debian/update-grub-legacy-ec2: fix to include kernels whose config has CONFIG_

[Bug 1647910] Re: hostname is set incorrectly if localhostname is fully qualified

2017-02-10 Thread Scott Moser
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-ini

[Bug 1647910] Re: hostname is set incorrectly if localhostname is fully qualified

2017-02-09 Thread Ɓukasz Zemczak
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.

[Bug 1647910] Re: hostname is set incorrectly if localhostname is fully qualified

2017-02-09 Thread Scott Moser
** Also affects: cloud-init (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: cloud-init Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium

[Bug 1647910] Re: hostname is set incorrectly if localhostname is fully qualified

2017-02-08 Thread Scott Moser
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/3

[Bug 1647910] Re: hostname is set incorrectly if localhostname is fully qualified

2017-02-06 Thread Brian Murray
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.

[Bug 1647910] Re: hostname is set incorrectly if localhostname is fully qualified

2017-02-02 Thread Brian Murray
** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/164