[OPNFLWPLUG-536] network elements (nodes, links, etc) are not always removed when running longevity test Created: 17/Aug/15  Updated: 27/Sep/21  Resolved: 08/Feb/16

Status: Resolved
Project: OpenFlowPlugin
Component/s: General
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Jamo Luhrsen Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Duplicate
duplicates OPNFLWPLUG-579 flows not removed from operational ds... Resolved
External issue ID: 4147

 Description   

two jobs that sometimes fail:
https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-periodic-longevity-lithium-redesign-only-beryllium/

https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-periodic-longevity-only-beryllium/

The basic flow of the job is to bring up 200 switches (mininet, linear topo) and
verify that they are connected and proper links via operational store. Then the
network is stopped and it's verified to be removed.

When the test fails, it seems to always be because the network has been stopped,
but there are still some things showing up in the call to /restconf/operational/network-topology:network-topology

It seems that it takes many iterations (e.g. 50-ish iterations taking 6-10 hours) to
hit this problem. No further root cause analysis has been done at this time.



 Comments   
Comment by Jozef Bacigal [ 08/Feb/16 ]

Probably the same as 4722

Generated at Wed Feb 07 20:32:44 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.