-
Type: Bug
-
Status: Closed (View Workflow)
-
Priority: Critical
-
Resolution: Done
-
Affects Version/s: 1.2.0
-
Fix Version/s: 1.8.0
-
Component/s: None
-
Labels:
-
Epic Link:
-
Sprint:Cardinal Sprint 6 (5/26-5/29)
It is observed that some of the flows that were added/modified during link down & link up (reroute test) are not deleted completely even after all the intents on ONOS are removed. This may be causing the subsequent
intent add and verify connectivity tests to fail in CHO.
Test Steps:
###############
1) Bring up ONOS and Mininet topology. (default flows on 25 devices are 75)
2) Enable fwd module and verify ping all PASS. (
3) Disable fwd module. (default flows are 125 after this step)
4) Add 300 host intents across all 25 hosts and verify ping all PASS.
5) Bring down some core links in topology and verify ping all PASS.
6) Bring up the links that were down and verify ping all PASS.
7) Remove all intents in ONOS.
9) Now the default flows on ONOS show >125 and repeat
of test steps 2 to 6 would start to fail.
Note: if the steps 5 and 6 are skipped I do not see the issue, so the flow cleanup issue seem to only happening after link down and link up test runs.
#######################################
Actual number of default flows on ONOS without
any intents before fwd module enable
########################################
onos> summary
node=10.128.40.41, version=1.2.0.admin~2015/06/01@03:16
nodes=3, devices=25, links=114, hosts=0, SCC(s)=1, flows=75, intents=0
onos>
#######################################
Actual number of default flows on ONOS without
any intents after fwd module disabled
(So, 125 flows should be on ONOS anytime if there are
no intents)
########################################
onos> summary
node=10.128.40.41, version=1.2.0.admin~2015/06/01@03:16
nodes=3, devices=25, links=114, hosts=0, SCC(s)=1, flows=125, intents=0
onos>
#######################################
Number of default flows on ONOS after
- Adding 300 host intents
- running reroute test
- removing all intents
########################################
onos> summary
node=10.128.40.41, version=1.2.0.admin~2015/06/01@03:16
nodes=3, devices=25, links=114, hosts=25, SCC(s)=1, flows=282, intents=87
onos> summary
node=10.128.40.41, version=1.2.0.admin~2015/06/01@03:16
nodes=3, devices=25, links=114, hosts=25, SCC(s)=1, flows=135, intents=0
onos> summary
node=10.128.40.41, version=1.2.0.admin~2015/06/01@03:16
nodes=3, devices=25, links=114, hosts=25, SCC(s)=1, flows=135, intents=0
onos> flows | grep Count
deviceId=of:0000000000000001, flowRuleCount=5
deviceId=of:0000000000000002, flowRuleCount=5
deviceId=of:0000000000000003, flowRuleCount=5
deviceId=of:0000000000000004, flowRuleCount=5
deviceId=of:0000000000000005, flowRuleCount=5
deviceId=of:0000000000000006, flowRuleCount=5
deviceId=of:0000000000000007, flowRuleCount=5
deviceId=of:0000000000000008, flowRuleCount=5
deviceId=of:0000000000000009, flowRuleCount=5
deviceId=of:000000000000000a, flowRuleCount=7
deviceId=of:000000000000000b, flowRuleCount=7
deviceId=of:000000000000000c, flowRuleCount=5
deviceId=of:000000000000000d, flowRuleCount=5
deviceId=of:000000000000000e, flowRuleCount=9
deviceId=of:000000000000000f, flowRuleCount=7
deviceId=of:0000000000000010, flowRuleCount=5
deviceId=of:0000000000000011, flowRuleCount=5
deviceId=of:0000000000000012, flowRuleCount=5
deviceId=of:0000000000000013, flowRuleCount=5
deviceId=of:0000000000000014, flowRuleCount=5
deviceId=of:0000000000000015, flowRuleCount=5
deviceId=of:0000000000000016, flowRuleCount=5
deviceId=of:0000000000000017, flowRuleCount=5
deviceId=of:0000000000000018, flowRuleCount=5
deviceId=of:0000000000000019, flowRuleCount=5
onos>