https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/TRNSPRTPCE-86 transportpce <p>It seems that when deleting a node in the topology-netconf, it is also deleted in the openroadm-network. Therefore, when later trying to delete it in the openroadm-network it does not exist anymore and a 404 is returned.</p> TRNSPRTPCE-86

Node disconnect tests in test_topology.py fail when trying to delete node in the openroadm-network

Bug Medium Verified Done Christophe BETOULE Jonas Mårtensson Tue, 12 Feb 2019 13:43:01 +0000 Fri, 3 Sep 2021 13:01:41 +0000 Mon, 29 Apr 2019 10:01:10 +0000 0 4 0 minutes 3 days <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=ojnas" class="user-hover" rel="ojnas">ojnas</a>jonas Can you please check if the new code resolve the problem?</p> <p>The patch does not solve the issue since nodes are still deleted in the openroadm-network after being deleted in the topology-netconf. Note that the problem does not always happen since it may take some time before nodes are really deleted but if you introduce a few seconds delay before deleting nodes in the openroadm-network you will see that the nodes does not exist anymore causing the test to fail with a 404.</p> <p>More tests fail with this patch since nodes are not deleted in the clli-network after the failure to delete nodes in the openroadm-network. This causes some later getClliNetwork tests to fail.</p> <p>OK, so Ahmed maybe the first action to take is to modify the topology test suite to add this timer and expose the problem and then try to investigate with colleagues what is wrong in the current workflow before proposing a fix ( should the 2 actions be merged or should we fix the java code ? )</p> <p>As you can see in the patch 4, I have added a timer to be sure that the node disconnection process is well taken into account, so I get the bug as it is described by Jonas. When nodes are disconnected at the topology-netconf layer, they will be automatically disconnected at the openroadm-network as well. Therefore, they will not be found by ODL and the test fails. So I delete the part that concerns the node disconnection at the openroam-network. However, at the end of the test suite when all the nodes are disconnected, the roadm-to-roadm links are still exist (failure of the last test). We will check with the colleagues if this is normal!</p> <p>The fact that the node is automatically removed from network topollogy when it disapear from the netconf topology fits with expected behavior. So I guess we should modify or remove the test to fit with this.expected behavior. for what concerns link, we expect something different. The link state shall change, but the link shall not disappear, because the link is built in a two srtep process. Discovery (leveraging lldp), and consolidation, checking consistency with data that describe a link and are not known by the device (SRLG, PMD,...). So we shall not test that the link does or does not exist. Note that they are currently user stories adressing the process of OMS information consolidation (<a href="https://jira.opendaylight.org/browse/TRNSPRTPCE-80" title="OMS attribute feeling" class="issue-link" data-issue-key="TRNSPRTPCE-80">TRNSPRTPCE-80</a>)</p> Development Rank 0|i03frz:0i002qgi Sprint Sprint 8 Sprint 9