...
commit 65b38cb6c0fa8ab371f9b9a7c8878e94f98a12d2 5be3e820cfeedd763b874e6581161f7e1a0e4850 (HEAD, origin/master, origin/HEAD, master)
Author: Hyunsun Moon [hyunsun.moon@gmailHIGUCHI Yuta [y-higuchi@ak.jp.nec.com]
AuthorDate: Fri Tue May 6 183 13:2751:37 42 2016 -0700
Commit: Hyunsun Moon [hyunsun.moon@gmail.comYuta HIGUCHI [y-higuchi@onlab.us]
CommitDate: Fri Mon May 6 189 23:2939:27 00 2016 -0700
Fixed consistent map event listener remove+0000
ONOS-4417 Remove OtuPort out of core.
HTML |
---|
<iframe src="https://onos-jenkins.onlab.us/job/HAclusterRestart/plot/Plot-HA/getPlot?index=2&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe> |
...
- 2.1 Assign switches to controllers - PASS
Case 8: Compare ONOS Topology view to Mininet topology -
...
FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS
FAIL
- ONOS topology don't match Mininet
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS
- 8.6 There is only one SCC - PASS
FAIL
- ONOS shows 0 SCCs
- 8.7 Device information is correct - PASS
FAIL
- Device information is incorrect
- 8.8 Links are correct - PASS
FAIL
- Links are incorrect
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - PASS
...
- 3.1 Install reactive forwarding app - PASS
- 3.2 Check app ids - PASS
- 3.3 Discovering Hosts( Via pingall for now ) - PASS
) - FAIL
- Reactive Pingall failed, one or more ping pairs failed
- 3.4 Uninstall reactive forwarding app - PASS
- 3.5 Check app ids - PASS
- 3.6 Add host intents via cli - PASS
FAIL
- Error looking up host ids
- 3.7 Intent Anti-Entropy dispersion - FAIL
PASS
Case 8: Compare ONOS Topology view to Mininet topology -
...
FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS
FAIL
- ONOS topology don't match Mininet
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS
- 8.6 There is only one SCC - PASS
FAIL
- ONOS shows 0 SCCs
- 8.7 Device information is correct - PASS
FAIL
- Device information is incorrect
- 8.8 Links are correct - FAIL
- Links are
- incorrect
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sending traffic across Intents -
...
FAIL
Ping across added host intents to check functionality and check the state of the intent
- 4.1 Check Intent state - PASS
- 4.2 Ping across added host intents - PASS
FAIL
- Intents have not been installed correctly, pings failed.
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
FAIL
- Intents have not been installed correctly, pings failed.
Case 5: Setting up and gathering data for current state -
...
FAIL
- 5.1 Check that each switch has a master - PASS
- 5.2 Get the Mastership of each switch from each controller - PASS
- 5.3 Check for consistency in roles from each controller - PASS
- 5.4 Get the intents from each controller - PASS
- 5.5 Check for consistency in Intents from each controller - PASS
- 5.6 Get the flows from each controller - PASS
- 5.7 Check for consistency in Flows from each controller - PASS
- 5.8 Get the OF Table entries - No Result
- 5.9 Start continuous pings - No Result
- 5.10 Collecting topology information from ONOS - No Result
- 5.11 Host view is consistent across ONOS nodes - PASS
FAIL
- ONOS nodes have different views of hosts
- 5.12 Each host has an IP address - PASS
- 5.13 Cluster view is consistent across ONOS nodes - PASS
- 5.14 Cluster view correct across ONOS nodes - PASS
FAIL
- ONOS shows 0 SCCs
- 5.15 Comparing ONOS topology to MN - PASS
FAIL
- ONOS7 hosts don't match Mininet
- 5.16 Device information is correct - PASS
FAIL
- Device information is incorrect
- 5.17 Links are correct - PASS
FAIL
- Links are incorrect
- 5.18 Hosts are correct - PASS
FAIL
- Hosts are incorrect
Case 14: Start Leadership Election app - PASS
...
- 6.1 Checking ONOS Logs for errors - No Result
- 6.2 Killing ONOS nodes - PASS
- 6.3 Checking if ONOS is up yet - PASS
Case 8: Compare ONOS Topology view to Mininet topology -
...
FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS
FAIL
- ONOS topology don't match Mininet
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS
- 8.6 There is only one SCC - PASS
FAIL
- ONOS shows 0 SCCs
- 8.7 Device information is correct - PASS
FAIL
- Device information is incorrect
- 8.8 Links are correct - PASS
FAIL
- Links are incorrect
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - PASS
...
- 3.1 Install reactive forwarding app - PASS
- 3.2 Check app ids - PASS
- 3.3 Discovering Hosts( Via pingall for now ) - PASS
FAIL
- Reactive Pingall failed, one or more ping pairs failed
- 3.4 Uninstall reactive forwarding app - PASS
- 3.5 Check app ids - PASS
- 3.6 Add host intents via cli - PASS
FAIL
- Error looking up host ids
- 3.7 Intent Anti-Entropy dispersion - FAIL
PASS
Case 7: Running ONOS Constant State Tests - FAIL
...
- 7.1 Check that each switch has a master - PASS
- 7.2 Read device roles from ONOS - PASS
- 7.3 Check for consistency in roles from each controller - FAIL
- consistency in roles from each controller - PASS
- 7.4 Get the intents and compare across all nodes - PASS
- 7.5 Check for consistency in Intents from each controller - PASS
- 7.6 Get the OF Table entries and compare to before component failure - FAIL
- Changes were found in the flow tables
- 7.7 Leadership Election is still functional - FAIL
- PASS
Case 4: Verify connectivity by sending traffic across Intents -
...
FAIL
Ping across added host intents to check functionality and check the state of the intent
- 4.1 Check Intent state - PASS
- 4.2 Ping across added host intents - PASS
FAIL
- Intents have not been installed correctly, pings failed.
- 4.3 Check leadership of topics - PASS
4.4 Wait a minute then ping again - PASS
- 4.4 Wait a minute then ping again - FAIL
- Intents have not been installed correctly, pings failed.
Case 15: Check that Leadership Election is still functional -
...
PASS
- 15.1 Run for election on each node - PASS
- 15.2 Check that each node shows the same leader and candidates - FAIL
- PASS
- 15.3 Find current leader and withdraw - FAIL
- PASS
- 15.4 Check that a new node was elected leader - FAIL
- PASS
- 15.5 Check that that new leader was the candidate of old leader - FAIL
- PASS
- 15.6 Run for election on old leader( just so everyone is in the hat ) - FAIL
- ) - PASS
- 15.7 Check that oldLeader is a candidate, and leader if only 1 node - FAIL
- PASS
Case 17: Check for basic functionality with distributed primitives - PASS
...
- 9.1 Kill Link between s3 and s28 - PASS
Case 8: Compare ONOS Topology view to Mininet topology -
...
FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS
FAIL
- ONOS topology don't match Mininet
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS
- 8.6 There is only one SCC - PASS
FAIL
- ONOS shows 0 SCCs
- 8.7 Device information is correct - PASS
FAIL
- Device information is incorrect
- 8.8 Links are correct - PASS
FAIL
- Links are incorrect
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sending traffic across Intents -
...
FAIL
Ping across added host intents to check functionality and check the state of the intent
- 4.1 Check Intent state - PASS
- 4.2 Ping across added host intents - PASS
FAIL
- Intents have not been installed correctly, pings failed.
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
FAIL
- Intents have not been installed correctly, pings failed.
Case 10: Restore a link to ensure that Link Discovery is working properly - PASS
...
- 10.1 Bring link between s3 and s28 back up - PASS
Case 8: Compare ONOS Topology view to Mininet topology -
...
FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS
FAIL
- ONOS topology don't match Mininet
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS
- 8.6 There is only one SCC - PASS
- FAIL
- ONOS shows 0 SCCs
- 8.7 Device information is correct - PASS
FAIL
- Device information is incorrect
- 8.8 Links are correct - PASS
FAIL
- Links are incorrect
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sending traffic across Intents -
...
FAIL
Ping across added host intents to check functionality and check the state of the intent
- 4.1 Check Intent state - PASS
- 4.2 Ping across added host intents - PASS
FAIL
- Intents have not been installed correctly, pings failed.
- 4.3 Check leadership of topics - PASS
4.4 Wait a minute then ping again - PASS
- 4.4 Wait a minute then ping again - FAIL
- Intents have not been installed correctly, pings failed.
Case 11: Killing a switch to ensure it is discovered correctly -
...
FAIL
- 11.1 Kill s5 - PASS
FAIL
- Failed to kill switch?
Case 8: Compare ONOS Topology view to Mininet topology -
...
FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS
FAIL
- ONOS topology don't match Mininet
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS
- 8.6 There is only one SCC - PASS
FAIL
- ONOS shows 0 SCCs
- 8.7 Device information is correct - PASS
FAIL
- Device information is incorrect
- 8.8 Links are correct - PASS
FAIL
- Links are incorrect
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sending traffic across Intents -
...
FAIL
Ping across added host intents to check functionality and check the state of the intent
- 4.1 Check Intent state - PASS
- 4.2 Ping across added host intents - PASS
FAIL
- Intents have not been installed correctly, pings failed.
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
FAIL
- Intents have not been installed correctly, pings failed.
Case 12: Adding a switch to ensure it is discovered correctly -
...
FAIL
- 12.1 Add back s5 - PASS
FAIL
- Failed to add switch?
Case 8: Compare ONOS Topology view to Mininet topology -
...
FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS
FAIL
- ONOS topology don't match Mininet
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS
- 8.6 There is only one SCC - PASS
FAIL
- ONOS shows 0 SCCs
- 8.7 Device information is correct - PASS
FAIL
- Device information is incorrect
- 8.8 Links are correct - PASS
FAIL
- Links are incorrect
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sending traffic across Intents -
...
FAIL
Ping across added host intents to check functionality and check the state of the intent
- 4.1 Check Intent state - PASS
- 4.2 Ping across added host intents - PASS
FAIL
- Intents have not been installed correctly, pings failed.
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
FAIL
- Intents have not been installed correctly, pings failed.
Case 13: Test Cleanup - PASS
...