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/NETVIRT-563 netvirt <p>Overview:<br/> ---------<br/> In netvirt automated test we observed that some elan interfaces remains in the model after their related VMs/ports were deleted</p> <p>For example:<br/> ------------<br/> In the following jenkins job you can see that at the end of the serie of tests and after the VMs and ports are already deleted the elan interfaces still exist </p> <p><a href="https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-nodl-v2-upstream-transparent-boron/446/archives/log.html.gz#s1-s1-s3" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-nodl-v2-upstream-transparent-boron/446/archives/log.html.gz#s1-s1-s3</a></p> <p>Look under:<br/> -----------<br/> Test: Delete networks --&gt; TEARDOWN --&gt; KEYWORD : Get Model Dump --&gt; For: @data models --&gt; config/elan:elan-interfaces</p> <p>As mentioned above, this issue was observed also during longevity test on a specific system and the none deletion of the elan interfaces caused system to be overloaded at some point</p> <p>Operating System: All<br/> Platform: All</p> NETVIRT-563

Elan interfaces are not always deleted after VM/port was deleted

Bug Resolved Cannot Reproduce Unassigned Mickael Strock-Vidal Thu, 23 Mar 2017 11:21:27 +0000 Thu, 19 Oct 2017 21:28:00 +0000 Thu, 6 Jul 2017 00:40:50 +0000 Boron General 0 2 <p>Analysis:<br/> ElanManager is listening on interface state changes, and eventually triggers InterfaceRemoveWorkerOnElanInterface, which eventually calls deleteElanInterfaceFromConfigDS.</p> <p>However, deleteElanInterfaceFromConfigDS is not performing the delete when the ietf-interface still exists in the config DS.</p> <p>When ietf-interface is eventually deleted (when the neutron config removal happens), nothing deletes the elan-interface – There is a comment inside handleNeutronPortDeleted that the ietf-interface deletion implicitly deletes the elan-interface, but it is wrong – This is only true when the interface-state still exits.</p> Development External issue ID 8058 External issue URL Rank 0|i01skn: