...
- 3.1 Install reactive forwarding app - PASS
- 3.2 Check app ids - PASS
- 3.3 Discovering Hosts( Via pingall for now ) - PASS
- 3.4 Uninstall reactive forwarding app - PASS
- 3.5 Check app ids - PASS
- 3.6 Add host intents via cli - PASS
- 3.7 Intent Anti-Entropy dispersion - PASS
Case 8: Compare ONOS Topology view to Mininet topology -
...
PASS
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - FAIL
- ONOS topology don't match Mininet
- PASS
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - FAIL Host information is incorrect
- 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 - FAIL
- ONOS shows 2 SCCs
- PASS
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - FAIL Links are incorrect
- PASS
- 8.9 Hosts are correct - FAIL Hosts are incorrect
- 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. 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 -
...
PASS
- 5.1 Check that each switch has a master - PASS
- 5.2 Get the Mastership of each switch from each controller - No Result
- 5.3 Read device roles from ONOS - PASS
- 5.4 Check for consistency in roles from each controller - PASS
- 5.5 Get the intents from each controller - PASS
- 5.6 Check for consistency in Intents from each controller - PASS
- 5.7 Get the flows from each controller - PASS
- 5.8 Check for consistency in Flows from each controller - PASS
- 5.9 Get the OF Table entries - No Result
- 5.10 Start continuous pings - No Result
- 5.11 Collecting topology information from ONOS - No Result
- 5.12 Host view is consistent across ONOS nodes - PASS
- 5.13 Each host has an IP address - FAIL The ip of at least one host is missing
- PASS
- 5.14 Cluster view is consistent across ONOS nodes - PASS
- 5.15 Cluster view correct across ONOS nodes - FAIL
- ONOS shows 2 SCCs
- PASS
- 5.16 Comparing ONOS topology to MN - FAIL ONOS7 hosts don't match Mininet
- PASS
- 5.17 Device information is correct - PASS
- 5.18 Links are correct - FAIL
- Links are incorrect
- PASS
- 5.19 Hosts are correct - FAIL
- Hosts are incorrect
- 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 Active node was elected leader? - PASS
Case 15: Check that Leadership Election is still functional -
...
PASS
- 15.1 Run for election on each node - FAIL
- At least one node failed to run for leadership
- Skipping the rest of this case.
Case 16: Install Primitives app - PASS
- 16.1 Install Primitives app - PASS
- 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 - No Result
Case 16: Install Primitives app - PASS
- 16.1 Install Primitives app - 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 Error incrementing default counter
- PASS
- 17.2 Get then Increment a default counter on each node - FAIL Error incrementing default counter
- PASS
- 17.3 Counters we added have the correct values - FAIL
- Added counters are incorrect
- 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 Error incrementing
- 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 Distributed Set get - FAIL Set elements are incorrect
- PASS
- 17.9 Distributed Set size - FAIL
- Set sizes are incorrect
- PASS
- 17.10 Distributed Set add() - FAIL
- Set add was incorrect
- PASS
- 17.11 Distributed Set addAll() - FAIL Set addAll was incorrect
- PASS
- 17.12 Distributed Set contains() - FAIL Set contains failed
- PASS
- 17.13 Distributed Set containsAll() - PASS
- 17.14 Distributed Set remove() - FAIL
- Set remove was incorrect
- PASS
- 17.15 Distributed Set removeAll() - FAIL
- Set removeAll was incorrect
- PASS
- 17.16 Distributed Set addAll() - FAIL Set addAll was incorrect
- PASS
- 17.17 Distributed Set clear() - FAIL
- Set clear was incorrect
- PASS
- 17.18 Distributed Set addAll() - FAIL
- Set addAll was incorrect
- PASS
- 17.19 Distributed Set retain() - FAIL Set retain was incorrect
- PASS
- 17.20 Partitioned Transactional maps put - PASS
- 17.21 Partitioned Transactional maps get - FAIL Partitioned Transactional Map values incorrect
- PASS
- 17.22 Get the value of a new value - FAIL
- Error getting atomic Value None, found: ['null', 'null', 'null', 'null', None, 'null', 'null']
- 17.23 Atomic Value set() - FAIL
- Error setting atomic Value[1, 1, 1, 1, -1, 1, 1]
- 17.24 Get the value after set() - FAIL
- Error getting atomic Value foo, found: ['foo', 'foo', 'foo', 'foo', None, 'foo', 'foo']
- PASS
- 17.23 Atomic Value set() - PASS
- 17.24 Get the value after set() - PASS
- 17.25 Atomic Value compareAndSet() - PASS
- 17.26 Get the value after compareAndSet() - PASS
- 17.27 Atomic Value getAndSet() - PASS
- 17.28 Get the value after getAndSet() - PASS
- 17.29 Atomic Value destory() - PASS
- 17.30 Get the value after destroy() - PASS
- 17.31 Work Queue add() - PASS
- 17.32 Check the work queue stats - PASS
- 17.33 Work Queue addMultiple 17.25 Atomic Value compareAndSet() - PASS
- 17.26 Get the value after compareAndSet() - FAIL
- Error getting atomic Value bar, found: ['bar', 'bar', 'bar', 'bar', None, 'bar', 'bar']
- 34 Check the work queue stats - PASS
- 17.35 Work Queue takeAndComplete() 1 17.27 Atomic Value getAndSet() - PASS
- 17.28 Get the value after getAndSet() - FAIL
- Error getting atomic Value: expected baz, found: ['baz', 'baz', 'baz', 'baz', None, 'baz', 'baz']
- 36 Check the work queue stats - PASS
- 17.37 Work Queue takeAndComplete() 2 17.29 Atomic Value destory() - PASS
- 17.30 Get the value after destroy() - FAIL
- Error getting atomic Value None, found: ['null', 'null', 'null', 'null', None, 'null', 'null']
- 38 Check the work queue stats - PASS
- 17.39 Work Queue destroy 17.31 Work Queue add() - PASS
- 17.32 40 Check the work queue stats - No Result PASS
Case 6: Restart entire ONOS cluster with backed up state - FAIL
...
- 6.1 Backup ONOS data - PASS
- 6.2 Checking ONOS Logs for errors - No Result
- 6.3 Uninstalling ONOS package - PASS
- 6.4 Installing ONOS package - PASS
- 6.5 Restore ONOS data - PASS
- 6.6 Restart ONOS nodes - No Result
- 6.7 Set up ONOS secure SSH - PASS
- 6.8 Checking ONOS service - PASS
- 6.9 Starting ONOS CLI sessions - FAIL
- Failed to rerun for election
Case 8: Compare ONOS Topology view to Mininet topology -
...
PASS
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - FAIL
- ONOS topology don't match Mininet
- PASS
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - FAIL Host information is incorrect
- 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
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - PASS
- 8.9 Hosts are correct - FAIL Hosts are incorrect
- PASS
- 8.10 Checking ONOS nodes - PASS
...
- 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 from each controller - PASS
- 7.5 Check for consistency in Intents from each controller - PASS
- 7.6 Leadership Election is still functional - PASS
Case 4: Verify connectivity by sending traffic across Intents - PASS
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
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - 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 - No Result
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
- Error incrementing default counter
- PASS
- 17.2 Get then Increment a default counter on each node - FAIL
- Error incrementing default counter
- PASS
- 17.3 Counters we added have the correct values - FAIL Added counters are incorrect
- 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
- Error incrementing default counter
- 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 Distributed Set get - PASS
- 17.9 Distributed Set size - PASS
- 17.10 Distributed Set add() - PASS
- 17.11 Distributed Set addAll() - PASS
- 17.12 Distributed Set contains() - PASS
- 17.13 Distributed Set containsAll() - PASS
- 17.14 Distributed Set remove() - PASS
- 17.15 Distributed Set removeAll() - PASS
- 17.16 Distributed Set addAll() - PASS
- 17.17 Distributed Set clear() - PASS
- 17.18 Distributed Set addAll() - PASS
- 17.19 Distributed Set retain() - PASS
- 17.20 Partitioned Transactional maps put - PASS
- 17.21 Partitioned Transactional maps get - PASS
- 17.22 Get the value of a new value - PASS
- 17.23 Atomic Value set() - PASS
- 17.24 Get the value after set() - PASS
- 17.25 Atomic Value compareAndSet() - PASS
- 17.26 Get the value after compareAndSet() - PASS
- 17.27 Atomic Value getAndSet() - PASS
- 17.28 Get the value after getAndSet() - PASS
- 17.29 Atomic Value destory() - PASS
- 17.30 Get the value after destroy() - PASS
- 17.31 Work Queue add() - PASS
- 17.32 Check the work queue stats - FAIL
- Work Queue stats incorrect
- PASS
- 17.33 Work Queue addMultiple() - PASS
- 17.34 Check the work queue stats - FAIL Work Queue stats incorrect
- PASS
- 17.35 Work Queue takeAndComplete() 1 - PASS
- 17.36 Check the work queue stats - FAIL Work Queue stats incorrect
- PASS
- 17.37 Work Queue takeAndComplete() 2 - PASS
- 17.38 Check the work queue stats - FAIL Work Queue stats incorrect
- stats - PASS
- 17.39 Work Queue destroy() - PASS
- 17.40 Check the work queue stats - PASS
...
- 9.1 Kill Link between s28 and s3 - PASS
Case 8: Compare ONOS Topology view to Mininet topology - PASS
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS
- 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
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - PASS
- 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 s28 and s3 back up - PASS
Case 8: Compare ONOS Topology view to Mininet topology - PASS
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS
- 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
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - PASS
- 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 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
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS
- 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
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - PASS
- 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 - PASS
- 12.1 Add back s5 - PASS
Case 8: Compare ONOS Topology view to Mininet topology - PASS
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS
- 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
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - PASS
- 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
...