From eb568b68d2522a21ad87c95e427024113aea07dd Mon Sep 17 00:00:00 2001 From: IWASE Yusuke Date: Thu, 19 Apr 2018 11:53:18 +0900 Subject: server: Withdraw routes when received RTM withdrawal Because the RTM is removed from adj-RIB-in before collecting the candidate routes to be withdrawn, the candidates are unexpectedly filtered before sending withdraw messages. Then on the peers, the VPN routes are left on. This patch fixes to selects candidates from the filtered paths and send withdraw messages as expected. Also resolves the TODO in "test/scenario_test/rtc_test.py". Signed-off-by: IWASE Yusuke --- test/scenario_test/rtc_test.py | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'test') diff --git a/test/scenario_test/rtc_test.py b/test/scenario_test/rtc_test.py index 3dfdef3f..d7d7b69c 100644 --- a/test/scenario_test/rtc_test.py +++ b/test/scenario_test/rtc_test.py @@ -94,9 +94,7 @@ class GoBGPTestBase(unittest.TestCase): self.g1.local("gobgp vrf del vrf1") time.sleep(2) self.assertEqual(2, len(self.g1.get_adj_rib_out(self.g2, rf='rtc'))) - # TODO: - # g2 should withdraw VPN routes when received a RTM withdrawal. - # self.assertEqual(1, len(self.g1.get_adj_rib_in(self.g2, rf='ipv4-l3vpn'))) + self.assertEqual(1, len(self.g1.get_adj_rib_in(self.g2, rf='ipv4-l3vpn'))) def test_06_rr_setup(self): # +------+ -- cgit v1.2.3