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-115 transportpce <p>As discussed in <a href="https://jira.opendaylight.org/browse/TRNSPRTPCE-86" title="Node disconnect tests in test_topology.py fail when trying to delete node in the openroadm-network" class="issue-link" data-issue-key="TRNSPRTPCE-86"><del>TRNSPRTPCE-86</del></a>, deleting a node in topology-netconf automatically also deletes it in openroadm-network, which caused topology tests to fail. This has been fixed by removing manual node deletions in openroadm-network from the tests. However, in test_topology.py there is still manual node deletions in clli-network. Looking at the deleteOpenROADMnode function in NetworkModelServiceImpl.java, it seems to me that the intention there is to automatically delete nodes also in clli-network. But this deletion seems to reference the topology-netconf nodeId when the clli-network nodeId is the clli, which is different.</p> TRNSPRTPCE-115

Deleting node in clli-network

Bug Medium Verified Done Olivier Renais Jonas Mårtensson Mon, 6 May 2019 16:28:59 +0000 Fri, 12 Jul 2019 09:02:02 +0000 Tue, 2 Jul 2019 13:34:22 +0000 0 1 0 minutes 2 hours <p>How was this resolved?</p> <p>Change back the status to unresolve since I am not sure we completely adress the comment. </p> <p>Agree with your view regarding what implements deleteOpenROADM Node. The intent is to delete the CLLI node as the Network node disappear. Fortunately there is a bug which leads at the end to the expected behavior (we try to delete a CLLI that corresponds to the node Id and does not exist : as an example if we have ROADMA in CLLI NodeA, we try to delete the CLLI ROADMA which does not exist). Indeed, we do not expect a CLLI to be removed from the topo just because one of the nodes hosted in this CLLI has disappeared. CLLI correspond to buildings/rooms. They are not supposed to be removed from the topology just becaus an equuipment in that room fails. Will put the bug in the next sprint (focused on topology and portmapping consolidation) and we will remove the function to delete CLLI. </p> Development Rank 0|i03frz:0i002qhz4i Sprint Sprint 9 Sprint 10