ovf: network config store routes under nic subnets 'routes' key

[Ryan Harper]

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.

[Server Team CI bot (server-team-bot)]

This bug is fixed with commit cb44ad6f to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=cb44ad6f

[Launchpad Janitor (janitor)]

This bug was fixed in the package cloud-init - 18.5-1-g5b065316-0ubuntu1

---------------
cloud-init (18.5-1-g5b065316-0ubuntu1) disco; urgency=medium

  * New upstream snapshot.
    - Update to pylint 2.2.2.
    - Release 18.5 (LP: #1808380)
    - tests: add Disco release [Joshua Powers]
    - net: render 'metric' values in per-subnet routes (LP: #1805871)
    - write_files: add support for appending to files. [James Baxter]
    - config: On ubuntu select cloud archive mirrors for armel, armhf, arm64.
      (LP: #1805854)
    - dhclient-hook: cleanups, tests and fix a bug on 'down' event.
    - NoCloud: Allow top level 'network' key in network-config. (LP: #1798117)
    - ovf: Fix ovf network config generation gateway/routes (LP: #1806103)

 -- Ryan Harper <email address hidden> Fri, 14 Dec 2018 14:45:46 -0600