Reviewed: https://review.opendev.org/c/openstack/charm-neutron-api-plugin-ovn/+/1015632 Committed: https://opendev.org/openstack/charm-neutron-api-plugin-ovn/commit/8795d59fa9480145713299f303e9c4dc57308bbb Submitter: "Zuul (22348)" Branch: stable/2024.1
commit 8795d59fa9480145713299f303e9c4dc57308bbb Author: Brian Haley <[email protected]> Date: Thu Sep 5 18:51:56 2024 -0400 Add support for new ovn_router_indirect_snat option With patches [0] and [1], there will be the need to configure the Neutron OVN ovn_router_indirect_snat option to True to enabled nested SNAT. Add support for it but default to False as it could cause both SNAT and floating IP issues if [1] is not applied in OVN. [0] https://review.opendev.org/c/openstack/neutron/+/926495 [1] https://patchwork.ozlabs.org/project/ovn/patch/[email protected]/ Closes-bug: #2051935 Conflicts: src/config.yaml src/reactive/neutron_api_plugin_ovn_handlers.py unit_tests/test_reactive_neutron_api_plugin_ovn_handlers.py Change-Id: I43b14e83ee9d46ceac813b0a9a770bd047b4f0ce Signed-off-by: Brian Haley <[email protected]> (cherry picked from commit 23eea788ca749c79fe189b124f6364f1c929b48a) -- 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 subnets directly connected to a router To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-api-plugin-ovn/+bug/2051935/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
