Routing table on the control node displays incorrect results on the WebUI

[lungdear]

Our setup:
OpenSDN version tag: R24.1
OpenStack version bobcat (2023.2)

Topology :

Project A
Subnet A: 192.168.1.0/24
Instance: 192.168.1.3

Project B
Subnet B: 192.168.2.0/24
Instance: 192.168.2.3

It was discovered that the routing table on the control node displays incorrect results on the WebUI.
We tested route leaking between projects by attaching a route target.

In Project A, the subnet 192.168.1.0/24 was attached to the route target 200:1, and similarly, in Project B, the subnet 192.168.2.0/24 was attached to the same route target.

After performing the configuration, the instance with IP 192.168.1.3 was able to ping across projects to 192.168.2.3 without any issues.

When viewing the routing table on the control node to display both projects, it correctly shows route leaking between the two projects.

Issue:

the issue arises when I remove the route target from one of the networks. The WebUI still displays the leaked routing information as if the route target is still in place, even though it has already been removed.

Currently, after removing the route target, the instances from both projects can no longer communicate with each other, indicating that the issue seems to be limited to the WebUI display only.

Verify after remove route-target

Verify after remove route-target. but the WebUI still display.

Expected Outcome:
Normally, when route leaking is canceled by removing the attached route target, the routing table on the control node for each project should display only its own routes.

However, in this case, one of the projects' routing tables incorrectly continues to display the leaked route from the other project, even after the route target has been removed.