Also, at least for the cloud-team's image generation, we should probably
switch to using "source /etc/network/interfaces.d/*", similar to what
d-i does and ifupdown will do. It won't help in this case, because the
provider that encountered the problem is using some other tooling to
generate their
On Tue, Aug 18, 2020 at 08:46:01PM +0100, Adam D. Barratt wrote:
> > https://github.com/canonical/cloud-init/commit/a6faf3acef02bd8cd4d46ac9efeebf24b3f21d81
>
> I must admit that I'm slightly confused by that commit.
>
> The rationale is that the default file written by ifupdown uses
>
On Tue, 2020-08-18 at 20:46 +0100, Adam D. Barratt wrote:
> On Tue, 2020-08-18 at 12:31 -0700, Stefano Rivera wrote:
> > Before 19.2 cloud-init wrote /etc/network/interfaces.d/50-cloud-
> > init.cfg
> > After 19.2 cloud-init wrote /etc/network/interfaces.d/50-cloud-init
> > Relevant upstream
On Tue, 2020-08-18 at 12:31 -0700, Stefano Rivera wrote:
> Hi Adam (2020.07.09_13:19:23_-0700)
> > The upload referenced by this bug report has been flagged for
> > acceptance into the proposed-updates queue for Debian buster.
>
> FWIW, this update included a change that broke the Debian images
Hi Adam (2020.07.09_13:19:23_-0700)
> The upload referenced by this bug report has been flagged for acceptance into
> the proposed-updates queue for Debian buster.
FWIW, this update included a change that broke the Debian images for at
least one hosting provider.
We noticed when provisioning a
package release.debian.org
tags 947351 = buster pending
thanks
Hi,
The upload referenced by this bug report has been flagged for acceptance into
the proposed-updates queue for Debian buster.
Thanks for your contribution!
Upload details
==
Package: cloud-init
Version:
6 matches
Mail list logo
