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 ** Changed in: neutron Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1718954 Title: network_data.json contains default routes for 2 interfaces Status in neutron: Invalid Status in OpenStack Compute (nova): Opinion Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1718954/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
