[Group.of.nepali.translators] [Bug 1802073] Re: No network in AWS (EC-Classic) after stopping and starting instance

2019-03-20 Thread Guilherme G. Piccoli
Problem is resolved in Bionic's latest version of cloud-init, released yesterday: $ dpkg -l | grep cloud-init ii cloud-init 18.5-45-g3554ffe8-0ubuntu1~18.04.1 I've manually upgraded the package after bringing-up my EC2 Classic instance, so notice the AWS image doesn't have the latest cloud-init

[Group.of.nepali.translators] [Bug 1802073] Re: No network in AWS (EC-Classic) after stopping and starting instance

2019-03-14 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init - 18.5-45-g3554ffe8-0ubuntu1 --- cloud-init (18.5-45-g3554ffe8-0ubuntu1) disco; urgency=medium * New upstream snapshot. - cloud-init-per: POSIX sh does not support string subst, use sed (LP: #1819222) -- Daniel Watkins Fri,

[Group.of.nepali.translators] [Bug 1802073] Re: No network in AWS (EC-Classic) after stopping and starting instance

2019-02-21 Thread Chad Smith
** Changed in: cloud-init (Ubuntu) Status: Confirmed => Fix Committed ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu