Reviewed: https://review.opendev.org/c/openstack/neutron/+/826828 Committed: https://opendev.org/openstack/neutron/commit/0fd168ae93176573575c61eab370e13a4cee34ce Submitter: "Zuul (22348)" Branch: master
commit 0fd168ae93176573575c61eab370e13a4cee34ce Author: Slawek Kaplonski <[email protected]> Date: Fri Jan 28 09:32:47 2022 +0100 Use elevated context to update router's external gateway When new defaults and scope enforcement are used in Neutron, elevated context needs to be used to update router's external gateway when new subnet is added to the external network. Otherwise, router can belongs to the other project than external network and it will not be updated at all. Closes-Bug: #1959331 Change-Id: I888ddf66a15cd20039ff26baccd170da128e1eb7 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1959331 Title: Router's external gateway isn't properly updated when new subnet is added Status in neutron: Fix Released Bug description: Steps to reproduce the issue: 1. Enable scope enforcement and new secure RBAC default policies in Neutron, 2. As project A create external network and IPv4 subnet 3. As project B create router and set external gateway using network created above, 4. As project A create IPv6 subnet in external network 5. Router's external gateway should be updated but it isn't. The issue happens after patch https://review.opendev.org/c/openstack/neutron/+/821208 was merged. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1959331/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
