yahoo-eng-team team mailing list archive

[John A Meinel <john@xxxxxxxxxxxxxxxxx>]

I believe there were issues with interfaces.d and Juju 2.1. I think in
either 2.2 or 2.3 we switched to parsing both /e/n/i and all included
files. We still only render a single /e/n/i that no longer has the
include directive, but we've read the contents of the included
locations.

So if you can specifically list an issue that we've seen, we can discuss
through it, but I think we're covered since Juju 2.2


** Changed in: juju
       Status: Triaged => 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/1712695

Title:
  Curtin network-passthrough configures /e/n/i.d/50-cloud-init.cfg
  instead of /e/n/i

Status in cloud-init:
  New
Status in curtin:
  Invalid
Status in juju:
  Fix Released
Status in MAAS:
  Incomplete

Bug description:
  When using curtin's network passthrough, it writes config in
  /etc/network/interfaces.d/50-cloud-init.cfg instead of
  /etc/network/interfaces.

  This is likely to break juju provided that (i believe) it parses
  /e/n/i to do their bridge configuration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1712695/+subscriptions