[Bug 1899299] Re: do-release-upgrade from Trusty to Xenial breaks cloud-init init-local on reboot

2021-04-27 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init - 21.1-19-gbad84ad4-0ubuntu1~18.04.2 --- cloud-init (21.1-19-gbad84ad4-0ubuntu1~18.04.2) bionic; urgency=medium * cherry-pick 83f6bbfb: Fix unpickle for source paths missing run_dir (#863) (LP: #1899299) * cherry-pick d132356c: fix

[Bug 1899299] Re: do-release-upgrade from Trusty to Xenial breaks cloud-init init-local on reboot

2021-04-27 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init - 21.1-19-gbad84ad4-0ubuntu1~16.04.2 --- cloud-init (21.1-19-gbad84ad4-0ubuntu1~16.04.2) xenial; urgency=medium * cherry-pick 83f6bbfb: Fix unpickle for source paths missing run_dir (#863) (LP: #1899299) * cherry-pick d132356c: fix

[Bug 1899299] Re: do-release-upgrade from Trusty to Xenial breaks cloud-init init-local on reboot

2021-04-27 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init - 21.1-19-gbad84ad4-0ubuntu1~20.04.2 --- cloud-init (21.1-19-gbad84ad4-0ubuntu1~20.04.2) focal; urgency=medium * cherry-pick 83f6bbfb: Fix unpickle for source paths missing run_dir (#863) (LP: #1899299) * cherry-pick d132356c: fix

[Bug 1899299] Re: do-release-upgrade from Trusty to Xenial breaks cloud-init init-local on reboot

2021-04-27 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init - 21.1-19-gbad84ad4-0ubuntu1~20.10.2 --- cloud-init (21.1-19-gbad84ad4-0ubuntu1~20.10.2) groovy; urgency=medium * cherry-pick 83f6bbfb: Fix unpickle for source paths missing run_dir (#863) (LP: #1899299) * cherry-pick d132356c: fix

[Bug 1899299] Re: do-release-upgrade from Trusty to Xenial breaks cloud-init init-local on reboot

2021-04-27 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init - 21.1-19-gbad84ad4-0ubuntu3 --- cloud-init (21.1-19-gbad84ad4-0ubuntu3) hirsute; urgency=medium * cherry-pick 83f6bbfb: Fix unpickle for source paths missing run_dir (#863) (LP: #1899299) * cherry-pick d132356c: fix error on

[Bug 1899299] Re: do-release-upgrade from Trusty to Xenial breaks cloud-init init-local on reboot

2021-04-27 Thread Ɓukasz Zemczak
** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899299 Title: do-release-upgrade from Trusty to Xenial breaks cloud-init init-local on reboot To manage

[Bug 1899299] Re: do-release-upgrade from Trusty to Xenial breaks cloud-init init-local on reboot

2021-04-27 Thread James Falcon
For Hirsute, this bug is not reproducible as it is only triggered by an upgrade from trusty. For regression testing, I ran the suite of cloud- init integration tests against hirsute. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1899299] Re: do-release-upgrade from Trusty to Xenial breaks cloud-init init-local on reboot

2021-04-23 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init - 21.1-19-gbad84ad4-0ubuntu3 --- cloud-init (21.1-19-gbad84ad4-0ubuntu3) hirsute; urgency=medium * cherry-pick 83f6bbfb: Fix unpickle for source paths missing run_dir (#863) (LP: #1899299) * cherry-pick d132356c: fix error on

[Bug 1899299] Re: do-release-upgrade from Trusty to Xenial breaks cloud-init init-local on reboot

2021-04-22 Thread James Falcon
Note that this bug is triggered only by an upgrade from trusty. This bug is not reproduceable on Bionic, Focal, or Groovy as none of those are supported upgrade paths from Trusty. For regression testing, I ran the suite of cloud-init integration tests for Xenial, Bionic, Focal, and Groovy. **

[Bug 1899299] Re: do-release-upgrade from Trusty to Xenial breaks cloud-init init-local on reboot

2021-04-22 Thread James Falcon
To trigger this bug on Xenial, I did the following: - launch a trusty instance - Perform 'do-release-upgrade' on the trusty instance - Reboot when complete - Verify WARNING and Traceback present in logs - Remove the log and reboot again - Verify WARNING and Traceback present after second boot To

[Bug 1899299] Re: do-release-upgrade from Trusty to Xenial breaks cloud-init init-local on reboot

2021-04-20 Thread Brian Murray
Hello Chad, or anyone else affected, Accepted cloud-init into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/21.1-19-gbad84ad4-0ubuntu1~20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this

[Bug 1899299] Re: do-release-upgrade from Trusty to Xenial breaks cloud-init init-local on reboot

2021-04-20 Thread Brian Murray
Hello Chad, or anyone else affected, Accepted cloud-init into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/21.1-19-gbad84ad4-0ubuntu1~20.10.2 in a few hours, and then in the -proposed repository. Please help us by testing this

[Bug 1899299] Re: do-release-upgrade from Trusty to Xenial breaks cloud-init init-local on reboot

2021-04-19 Thread James Falcon
** Description changed: + === Begin SRU Template === + [Impact] + The 'Paths' class has a 'run_dir' attribute that was introduced since the release of Trusty. Because of this, performing a `do-release-upgrade` on Trusty followed by a reboot will have cloud-init fail with a traceback. + + The

[Bug 1899299] Re: do-release-upgrade from Trusty to Xenial breaks cloud-init init-local on reboot

2021-04-19 Thread James Falcon
A fix for this can be found at https://github.com/canonical/cloud- init/commit/83f6bbfbe5b924be61a3c098f4202377d69c8947 ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Focal) Importance: Undecided Status: New

[Bug 1899299] Re: do-release-upgrade from Trusty to Xenial breaks cloud-init init-local on reboot

2021-04-14 Thread Paride Legovini
I just noticed this affects torkoal (cloud-init 20.4.1-0ubuntu1~18.04.1). On reboot we have: [ 36.428237] cloud-init[4810]: failed run of stage modules-config [ 36.428373] cloud-init[4810]: [ 36.428434] cloud-init[4810]: