[Yahoo-eng-team] [Bug 1712695] Re: Curtin network-passthrough configures /e/n/i.d/50-cloud-init.cfg instead of /e/n/i

2019-02-22 Thread Dan Watkins
** No longer affects: cloud-init -- 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

[Yahoo-eng-team] [Bug 1712695] Re: Curtin network-passthrough configures /e/n/i.d/50-cloud-init.cfg instead of /e/n/i

2018-01-31 Thread John A Meinel
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

[Yahoo-eng-team] [Bug 1712695] Re: Curtin network-passthrough configures /e/n/i.d/50-cloud-init.cfg instead of /e/n/i

2017-12-06 Thread Lee Trager
Adding juju to verify if they are looking at /etc/network/interfaces. ** Also affects: juju Importance: Undecided Status: New ** Changed in: maas Status: New => Incomplete -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is

[Yahoo-eng-team] [Bug 1712695] Re: Curtin network-passthrough configures /e/n/i.d/50-cloud-init.cfg instead of /e/n/i

2017-08-23 Thread Ryan Harper
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