[OVN] Neutron requests answered with RouterNotFound
Bug #1961967 reported by
Elvira García Ruiz
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Undecided
|
Elvira García Ruiz |
Bug Description
A recently merged patch [0] has introduced a race condition when creating or updating an OVN Logical Router Port. If the mtu is changed on an external network, the set_gateway_mtu function will look to update all related logical router ports.
There is a small chance in this operation that one of those routers got deleted along the way. This raises a RouterNotFound error and fails.
More info and testing details available on this Bugzilla [1]
[0] https:/
[1] https:/
Fix proposed: https:/
Changed in neutron: | |
assignee: | nobody → Elvira García Ruiz (elviragr) |
Changed in neutron: | |
status: | New → In Progress |
tags: | added: ovn |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/c/openstack /neutron/ +/830509 /opendev. org/openstack/ neutron/ commit/ b2421b01e5bc126 9458b421643c13b 620cdaccaf
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit b2421b01e5bc126 9458b421643c13b 620cdaccaf
Author: Elvira García <email address hidden>
Date: Tue Feb 22 18:56:55 2022 +0100
[OVN] Handle RouterNotFound exception in set_gateway_mtu
When handling multiple router update/delete petitions, if they are
executed at the same time, there is a chance that the set_gateway_mtu
tries to update a no-longer-existing router, triggering a
RouterNotFound error from the _get_router_ports function. Now, if there
is not a router, the _get_router_ports function will return an empty
list instead of raising the error.
Closes-Bug: #1961967 4cd58c1d3a278d8 f3ffcda0a64
Signed-off-by: Elvira García <email address hidden>
Change-Id: Ic54214ca496527