...
HTML |
---|
<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/HAsanity_master_20-builds_graph.jpg", alt="HAsanity", style="width:525px;height:350px;border:0"> |
commit 555617a9f918209cfd6b2c283d6a80638f83c17a 724037b5fd769c53d69bf0039d6c0bcb18e480e6 (HEAD -] master, origin/master, origin/HEAD, master)
Author: Davide Scano pier [dpier@opennetworking.scano89@gmail.comorg]
AuthorDate: Wed Fri Jun 3 2112 18:4748:13 37 2020 +0200
Commit: Davide Scano pier [dpier@opennetworking.scano89@gmail.comorg]
CommitDate: Thu Sat Jun 4 0727 12:2345:58 11 2020 +0000
INT app gui20200
[AETHER-77] onos-diagnostics-k8s
Case 1: Constructing test variables and building ONOS package - PASS
...
- 16.1 Install Primitives app - PASS
Case 17: Check for basic functionality with distributed primitives -
...
FAIL
Test the methods of the distributed primitives (counters and sets) throught the cli
- 17.1 Increment then get a default counter on each node - PASS FAIL
- Error incrementing default counter
- 17.2 Get then Increment a default counter on each node - PASS FAIL
- Error incrementing default counter
- 17.3 Counters we added have the correct values - PASS FAIL
- Added counters are incorrect
- 17.4 Add -8 to then get a default counter on each node - PASS FAIL
- Error incrementing default counter
- 17.5 Add 5 to then get a default counter on each node - PASS FAIL
- Error incrementing default counter
- 17.6 Get then add 5 to a default counter on each node - PASS FAIL
- Error incrementing default counter
- 17.7 Counters we added have the correct values - PASS FAIL
- Added counters are incorrect
- 17.8 Distributed Set get - PASS FAIL
- Set elements are incorrect
- 17.9 Distributed Set size - PASS FAIL
- Set sizes are incorrect
- 17.10 Distributed Set add() - PASS FAIL
- Set add was incorrect
- 17.11 Distributed Set addAll() - PASS FAIL
- Set addAll was incorrect
- 17.12 Distributed Set contains() - PASS FAIL
- Set contains failed
- 17.13 Distributed Set containsAll() - PASS
- 17.14 Distributed Set remove() - PASS FAIL
- Set remove was incorrect
- 17.15 Distributed Set removeAll() - PASS FAIL
- Set removeAll was incorrect
- 17.16 Distributed Set addAll() - PASS FAIL
- Set addAll was incorrect
- 17.17 Distributed Set clear() - PASS FAIL
- Set clear was incorrect
- 17.18 Distributed Set addAll() - PASS FAIL
- Set addAll was incorrect
- 17.19 Distributed Set retain() - PASS FAIL
- Set retain was incorrect
- 17.20 Partitioned Transactional maps put - PASS FAIL
- Partitioned Transactional Map put values are incorrect
- 17.21 Partitioned Transactional maps get - PASS FAIL
- Partitioned Transactional Map values incorrect
- 17.22 Get the value of a new value - PASS FAIL
- Error getting atomic Value None, found: ['null', 'null', 'null', 'null', None]
- 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() - PASS
- 17.34 Check the work queue stats - PASS
- 17.35 Work Queue takeAndComplete() 1 - PASS
- 17.36 Check the work queue stats - PASS
- 17.37 Work Queue takeAndComplete() 2 - PASS
- 17.38 Check the work queue stats - PASS
- 17.39 Work Queue destroy() - PASS
- 17.40 Check the work queue stats - PASS
Case 6: Wait 60 seconds instead of inducing a failure - 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 7: Running ONOS Constant State Tests - 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 Compare switch roles from before failure - PASS
- 7.5 Get the intents from each controller - PASS
- 7.6 Check for consistency in Intents from each controller - PASS
- 7.7 Compare current intents with intents before the failure - PASS
- 7.8 Get the OF Table entries and compare to before component failure - PASS
- 7.9 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
- FAIL
- Error setting atomic Value[1, 1, 1, 1, -1]
- 17.
- 17.1 Increment then get a default counter on each node - PASS
- 17.2 Get then Increment a default counter on each node - PASS
- 17.3 Counters we added have the correct values - PASS
- 17.4 Add -8 to then get a default counter on each node - PASS
- 17.5 Add 5 to then get a default counter on each node - PASS
- 17.6 Get then add 5 to a default counter on each node - PASS
- 17.7 Counters we added have the correct values - 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 FAIL
- Error getting atomic Value foo, found: ['foo', 'foo', 'foo', 'foo', None]
- 17.25 Atomic Value compareAndSet() - PASS
- 17.26 Get the value after compareAndSet() - PASS FAIL
- Error getting atomic Value bar, found: ['bar', 'bar', 'bar', 'bar', None]
- 17.27 Atomic Value getAndSet() - PASS
- 17.28 Get the value after getAndSet() - PASS FAIL
- Error getting atomic Value: expected baz, found: ['baz', 'baz', 'baz', 'baz', None]
- 17.29 Atomic Value destory() - PASS
- 17.30 Get the value after destroy() - PASS FAIL
- Error getting atomic Value None, found: ['null', 'null', 'null', 'null', None]
- 17.31 Work Queue add() - PASS
- 17.32 Check the work queue stats - PASS
- 17.33 Work Queue addMultiple() - PASS
- 17.34 Check the work queue stats - PASS
- 17.35 Work Queue takeAndComplete() 1 - PASS
- 17.36 Check the work queue stats - PASS
- 17.37 Work Queue takeAndComplete() 2 - PASS
- 17.38 Check the work queue stats - PASS
- 17.39 Work Queue destroy() - PASS
- 17.40 Check the work queue stats - PASS
Case 9: Turn off a link to ensure that Link Discovery is working properly - 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 - 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 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 - 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 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 - 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 12: Adding a switch to ensure it is discovered correctly - PASS
- 12.1 Add back s5 - PASS
- No Result
Case 6: Wait 60 seconds instead of inducing a failure - PASS
Case 8: Compare ONOS Topology view to Mininet
...
topology
...
- 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 13: Test Cleanup - PASS
...