Bug#931173: Configuring static networking via NoCloud with Network Config Version 2 does not work
On 12/31/19 1:13 PM, Christian Tramnitz wrote:
> On Tue, 13 Aug 2019 10:04:03 +0200 Bastian Blank <waldi@debian.org> wrote:
>> - cloud-init write the config file using a name that is ignored by
>> ifupdown. The filename is "50-cloud-init.cfg" and everything with "-"
>> or "_" in it is ignored. (wtf?)
>
> No, it's the other way around:
> File names may *only* include alphanumeric and "-" + "_" but not a dot.
> So the ".cfg" is the part that is causing the problem.
>
> This has already been addressed upstream, see
> https://github.com/canonical/cloud-init/commit/a6faf3acef02bd8cd4d46ac9efeebf24b3f21d81#diff-6bf578623d31fa6e19b21138b2c41e8e
>
> So I'd suggest to backport this patch:
> https://github.com/canonical/cloud-init/commit/a6faf3acef02bd8cd4d46ac9efeebf24b3f21d81.patch
This is included in cloud-init 19.3 which is currently in Sid/Testing,
and as our current plan is to backport 19.3 as the new version for
buster-proposed-updates, this may be solved with this upgrade. Let's
wait and see what the stable release team says.
Cheers,
Thomas Goirand (zigo)
Reply to: