yahoo-eng-team team mailing list archive

[Ryan Harper <1712695@xxxxxxxxxxxxxxxxxx>]

They cannot just parse /etc/network/interfaces;  curtin has always
written out an eni that includes a source
/etc/network/interfaces.d/*.cfg (meaning juju has a bug if they don't
read all eni configs).

Anyone parsing eni needs to read in all of the configs.   In which case,
they would pickup any configs that cloud-init renders (including
/etc/network/interfaces.d/50-cloud-init.cfg

outside of maas, juju has to parse cloud-init rendered network config
(on clouds) anyhow which is always written at the location specified in
this bug.

** Changed in: curtin
       Status: New => Invalid

-- 
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 MAAS:
  New

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