network_data.json contains default routes for 2 interfaces

[Scott Moser]

On an OpenStack Ocata install a guest with two network interfaces
attached is provided with network_data.json that describes 2 default
routes.

See attached network_data.json and (pretty formatted network_data-pretty.json).
Also note that the reporter ran 'dhclient -v' which created the attached
dhclient.leases file. Only one of the dhcp servers returns a 'routers'
option. That would seem to indicate that the platform has some distinction.

Cloud-init renders the networking in /etc/network/interfaces and ends
up with 2 default routes, which doesn't do what the user wanted.

This issue was originally raised in freenode #cloud-init.
There is discussion surrounding it with the original reporter at:
  https://irclogs.ubuntu.com/2017/09/22/%23cloud-init.html

Related bugs:
 * bug 1717560: allow to have no default route in DHCP host routes

[Sylvain Bauza (sylvain-bauza)]

Nova is no longer providing L3 and L4 network layers for the VMs unless you use nova-net which was deprecated in Newton and only working in Ocata if you use Cells V1.

So I guess your problem is probably related to Neutron but you should explain more about the issue I guess.

[Lukas Stehlik (stelucz)]

see bug https://bugs.launchpad.net/neutron/+bug/1717560

[Boden R (boden)]

Best I can tell, from a neutron perspective this is now being driven under the referenced RFE [1].
Under that assumption I'm getting this one off the bug queue.
If [1] doesn't cover this defect, please feel free to open and provide some details on how this differs from [1].

Thanks

[1] https://bugs.launchpad.net/neutron/+bug/1717560