This bug was fixed in the package cloud-init - 18.2-41-g3b712fce- 0ubuntu1 --------------- cloud-init (18.2-41-g3b712fce-0ubuntu1) cosmic; urgency=medium
* debian/new-upstream-snapshot: Remove script, now maintained elsewhere. * New upstream snapshot. - tests: do not rely on host /proc/cmdline in test_net.py [Lars Kellogg-Stedman] (LP: #1769952) - ds-identify: Remove dupe call to is_ds_enabled, improve debug message. - SmartOS: fix get_interfaces for nics that do not have addr_assign_type. - tests: fix package and ca_cert cloud_tests on bionic (LP: #1769985) - ds-identify: make shellcheck 0.4.6 happy with ds-identify. - pycodestyle: Fix deprecated string literals, move away from flake8. - azure: Add reported ready marker file. [Joshua Chan] (LP: #1765214) - tools: Support adding a release suffix through packages/bddeb. - FreeBSD: Invoke growfs on ufs filesystems such that it does not prompt. [Harm Weites] (LP: #1404745) - tools: Re-use the orig tarball in packages/bddeb if it is around. - netinfo: fix netdev_pformat when a nic does not have an address assigned. (LP: #1766302) - collect-logs: add -v flag, write to stderr, limit journal to single boot. (LP: #1766335) - IBMCloud: Disable config-drive and nocloud only if IBMCloud is enabled. (LP: #1766401) - Add reporting events and log_time around early source of blocking time -- Scott Moser <smo...@ubuntu.com> Fri, 11 May 2018 16:37:02 -0400 ** Changed in: cloud-init (Ubuntu Cosmic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1766401 Title: full config file wiped after apt-upgrade issued Status in cloud-images: New Status in cloud-init: Fix Committed Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Released Status in cloud-init source package in Artful: Fix Released Status in cloud-init source package in Bionic: Confirmed Status in cloud-init source package in Cosmic: Fix Released Bug description: === Begin SRU Template === [Impact] Upgrades of cloud-init on official Ubuntu 16.04 and 17.10 images running on IBM public cloud will be unreachable after a reboot. This is because cloud-init incorrectly recognizes the newly added 'IBMCloud' as the datasource to use and skips use of the previously used ConfigDrive or NoCloud datasource. This is because a.) Official 16.04 and 17.10 images of Ubuntu have seeded data in their /var/lib/cloud/seed/ directory that was used on first boot and should be continued to be used. b.) IBMCloud's datasource in some scenarios appears looks similar to that of Config Drive. The version of cloud-init in xenial and artful checks to disable config-drive in order to identify the IBMCloud datasource. That should not happen unless the IBMCloud datasource is enabled, which is configured off in those images. The fix is to continue using the existing datasource on those images. [Test Case] * Launch an image on IBM public cloud. * add -proposed * apt-get update && apt-get install cloud-init * reboot * ssh back in If you are able to ssh back in, then this bug has been fixed. [Regression Potential] This specific fix is tightly contained down the path involved in IBM cloud. The most likely failure scenario would be failure in 18.04 images which do not have the additional datasources built into the images. [Other Info] Upstream commit at https://git.launchpad.net/cloud-init/commit/?id=11172924 === End SRU Template === file: 50-cloud-init.cfg wiped of it's initial (working) configuration after a standard apt-upgrade was issued. Cloud provider is SoftLayer. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1766401/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp