The L2VPN is removed after changing ports to down

[gretelliz]

OXPO sends a topology update with a Port Down and that port is part of an inter-domain link.

Here the L2VPN is removed after changing a node to down

(see test_021_port_in_inter_domain_link_down_no_reprov)

[YufengXin]

@gretelliz Could you please clarify this issue: 1. The title said "node down", but the test case said "port down"? 2. Why should the affected L2VPN not be removed?
@congwang09

[gretelliz]

Hello @YufengXin, @congwang09

I was reviewing the test related to this issue and noticed that the behavior has changed since the last time I analyzed it.

The purpose of this test is to create an L2VPN, set a port to down, verify that the L2VPN status changes to down, then restore the port to up and check that the L2VPN status returns to up.

First, I’d like to clarify that this test is related to a port, not a node, as correctly stated in the use case description and reflected in the test implementation itself. The confusion may come from the xfail description, which incorrectly mentions "node" instead of "port."

In this test two ports are set to down (instead of one) to prevent further reprovisioning due to the topology. In this scenario, when both ports are set to down, the L2VPN status changes to down as expected, but when the ports are restored to up, the L2VPN status remains down.

Previously, the issue was that the L2VPN was deleted when the ports went down, rather than simply changing its status to down.

[YufengXin]

The title of this issue says "...nodes to down"

[gretelliz]

Hello @YufengXin, apologies for the confusion — it should be port rather than node.
I updated the issue title accordingly.

In any case, please keep in mind the comment I left earlier. Based on my most recent check, the problem appears to be different from what I originally saw.