Public bug reported:
When generating a network-config (v1), any routes should be provided under the
scope of a subnet.
For some renderers (eni) using the top-level routes in the config will
'accidentally' work due to ifupdown implementation, however, routes should
instead be scoped under a network devices subnets.
Other renderers like netplan and sysconfig, need to know the network device
name to ensure the route is created correctly.
Fixing this allows OVF network customizations which use a GATEWAY value
and not primary to include the gateway configuration. This was
partially address in LP: #1766538 however it does not work for all net
renderers.
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806103
Title:
ovf: network config store routes under nic subnets 'routes' key
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1806103/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
