ovf: network config store routes under nic subnets 'routes' key
Bug #1806103 reported by
Ryan Harper
on 2018-11-30
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | cloud-init (Ubuntu) |
Undecided
|
Unassigned | ||
Bug Description
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.
Related branches
~raharper/cloud-init:fix/ovf-imc-network-config-gateway-routes
- Scott Moser: Approve on 2018-12-03
- Server Team CI bot: Approve (continuous-integration) on 2018-12-03
-
Diff: 173 lines (+64/-14)3 files modifiedcloudinit/cmd/devel/net_convert.py (+10/-5)
cloudinit/sources/helpers/vmware/imc/config_nic.py (+2/-3)
tests/unittests/test_vmware_config_file.py (+52/-6)
To post a comment you must log in.
This bug is fixed with commit cb44ad6f to cloud-init on branch master.
To view that commit see the following URL:
https:/