It was my understanding that the issue reported here stemmed from the fact that change [1] recklessly replaced the host's gateway without being cognizant of the networking ranges at hand.
Can you please provide evidence to any recent failure you have observed? Is the failure mode the same?
It is my understanding that this is a setup issue; neutron operates based on the details that are being fed to it, and takes over based on the assumption that the deployer has ensured that underlay and overlay have been decoupled. What sort of solution would you expect to see being provided by neutron itself?
Monty,
It was my understanding that the issue reported here stemmed from the fact that change [1] recklessly replaced the host's gateway without being cognizant of the networking ranges at hand.
Can you please provide evidence to any recent failure you have observed? Is the failure mode the same?
It is my understanding that this is a setup issue; neutron operates based on the details that are being fed to it, and takes over based on the assumption that the deployer has ensured that underlay and overlay have been decoupled. What sort of solution would you expect to see being provided by neutron itself?
[1] https:/ /review. openstack. org/#/c/ 356026/ 4/lib/neutron_ plugins/ services/ l3@345