Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
HAclusterRestart at
...
19 Nov 2015
...
03:
...
21:
...
54
commit b0e1dd018a160134bc8fdd874a787f2bad3fc6dd dd415c31d8a0d57fbe4a3ab721e2a95d7afa4495 (HEAD, origin/onos-1.3, onos-1.3)
Author: Jonathan Hart [jono@onlab.us]
AuthorDate: Wed Sep 23 17:54:11 2015 -0700Mon Nov 16 10:56:20 2015 -0800
Commit: Jonathan Hart [jono@onlab.us]
CommitDate: Thu Sep 24 13:22:23 2015 -0700
IntentManager: Don't compile all failed intents on every event
...
Mon Nov 16 14:14:24 2015 -0800
Protect against exceptions thrown in application's packet processors.
Case 1: Setting up test environment - PASS
...
Case 5: Setting up and gathering data for current state - PASS
- 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
- 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
- 5.15 Comparing ONOS topology to MN - PASS
- 5.16 Device information is correct - PASS
- 5.17 Links are correct - PASS
- 5.18 Hosts are correct - PASS
Case 14: Start Leadership Election app - PASS
- 14.1 Install leadership election app - PASS
- 14.2 Run for election on each node - PASS
- 14.3 Check that each node shows the same leader - PASS
Case 16: Install Primitives app - PASS
- 16.1 Install Primitives app - PASS
...
Case 6: Restart entire ONOS cluster - 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 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 - 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 - PASS
...
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 - PASS
- 15.3 Find current leader and withdraw - PASS
- 15.4 Check that a new node was elected leader - PASS
- 15.5 Check that that new leader was the candidate of old leader - PASS
- 15.6 Run for election on old leader( just so everyone is in the hat ) - PASS
- 15.7 Check that oldLeader is a candidate, and leader if only 1 node - PASS
Case 17: Check for basic functionality with distributed primitives -
...
PASS
Test the methods of the distributed primitives (counters and sets) throught the cli
- 17.1 Increment then get a default counter on each node - FAIL
- PASS
- 17.2 Get then Increment a default counter on each node - FAIL
- PASS
- 17.3 Counters we added have the correct values - FAIL
- PASS
- 17.4 Add -8 to then get a default counter on each node - FAIL
- Error incrementing default counter
- PASS
- 17.5 Add 5 to then get a default counter on each node - FAIL
- a default counter on each node - PASS
- 17.6 Get then add 5 to a default counter on each node - FAIL
- Error incrementing default counter
- PASS
- 17.7 Counters we added have the correct values - FAIL
- Added counters are incorrect
- PASS
- 17.8 Increment and get an in-memory counter on each node - PASS
- 17.9 Get then Increment a in-memory counter on each node - PASS
- 17.10 Counters we added have the correct values - PASS
- 17.11 Add -8 to then get a in-memory counter on each node - FAIL
- PASS
- 17.12 Add 5 to then get a in-memory counter on each node - FAIL
- Error incrementing in-memory counter
- PASS
- 17.13 Get then add 5 to a in-memory counter on each node - PASS
- 17.14 Counters we added have the correct values - PASS
- 17.15 Check counters are consistant across nodes - PASS
- 17.16 Counters we added have the correct values - PASS
- 17.17 Distributed Set get - PASS
- 17.18 Distributed Set size - PASS
- 17.19 Distributed Set add() - FAIL
- Set add was incorrect
- PASS
- 17.20 Distributed Set addAll() - PASS
- 17.21 Distributed Set contains() - PASS
- 17.22 Distributed Set containsAll() - PASS
- 17.23 Distributed Set remove() - PASS
- 17.24 Distributed Set removeAll() - PASS
- 17.25 Distributed Set addAll() - PASS
- 17.26 Distributed Set clear() - PASS
- 17.27 Distributed Set addAll() - FAIL
- PASS
- 17.28 Distributed Set retain() - PASS
- 17.29 Partitioned Transactional maps put - PASS
- 17.30 Partitioned Transactional maps get - PASS
- 17.31 In-memory Transactional maps put - PASS
- 17.32 In-Memory Transactional maps get - PASS
Case 9: Turn off a link to ensure that Link Discovery is working properly - PASS
- 9.1 Kill Link between s3 and s28 - PASS
...
- 4.1 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS
FAIL
- Intents are not all in INSTALLED state
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - 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
...
- 4.1 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS
FAIL
- Intents are not all in INSTALLED state
- 4.3 Check leadership of topics - 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 - PASS
- 11.1 Kill s5 - PASS
Case 8: Compare ONOS Topology view to Mininet topology - PASS
...
- 4.1 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS
FAIL
- Intents are not all in INSTALLED state
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - FAIL
- Intents have not been installed correctly, pings failed.
Case 12: Adding a switch to ensure it is discovered correctly - PASS
- 12.1 Add back s5 - PASS
Case 8: Compare ONOS Topology view to Mininet topology - PASS
...
- 4.1 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS
FAIL
- Intents are not all in INSTALLED state
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - FAIL
- Intents have not been installed correctly, pings failed.
Case 13: Test Cleanup - PASS
- 13.1 Killing tcpdumps - No Result
- 13.2 Stopping Mininet - PASS
- 13.3 Checking ONOS Logs for errors - No Result