BTW, Terry Wilson found the original neutron bug where this behavior was
introduced in neutron, allowing all subnets indirectly connected to a
router to use the default SNAT address.
https://bugs.launchpad.net/neutron/+bug/1386041
Wanted to make sure that was documented.
--
You received this
Just adding issue Rodolfo raised with the OVN team at Red Hat:
https://issues.redhat.com/browse/FDP-448
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051935
Title:
[OVN] SNAT only happens for
So just some additional information.
The reporter confirmed their cloud is running HA routers, but not DVR.
And talking with Rodolfo on irc reminded me of a proposed change that I
finally found:
https://review.opendev.org/c/openstack/neutron/+/890459
And the bug for that is:
Hello Brian:
First of all, I don't have a devstack deployed environment. I have a
multinode setup with 3 controllers and 2 compute nodes, so I needed to
change the commands provided.
10.0.0.0/24 is the external network configured in my deployment. The other
resources are:
* router_ext:
**
Ok, as I was asked about the case of 3 nested routers (i.e. a network on
a private subnet behind 3 total routers, 2 nested on their own private
networks), I've tested that as well. Same results - shows a clear
regression from ML2/OVS to OVN.
Again, I used devstack, this was the latest commit in
These are the settings I used for my ml2/ovs devstack:
Q_AGENT=openvswitch
Q_ML2_PLUGIN_MECHANISM_DRIVERS=openvswitch
Q_ML2_TENANT_NETWORK_TYPE=vxlan
enable_service q-agt
enable_service q-l3
enable_service q-dhcp
enable_service q-meta
disable_service ovn-controller
disable_service ovn-northd
