...
HTML |
---|
<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/HAbackupRecover_master_20-builds_graph.jpg", alt="HAbackupRecover", style="width:525px;height:350px;border:0"> |
commit 8b17e0eec5332f6db915af95ee8ff271848642b7 b53d626fb03195129c0ec0802e1f953f85dcbef8 (HEAD -] master, origin/master, origin/HEAD, master)
Author: Jordan Halterman pierventre [jordan@opennetworkingpier@opennetworking.org]
AuthorDate: Tue Dec 18 13:57:36 2018 -0800Wed Sep 22 11:24:38 2021 +0200
Commit: Ray Milkey [ray@opennetworkingPier Luigi Ventre [pier@opennetworking.org]
CommitDate: Tue Dec 18 22:50:15 2018 +0000
Upgrade to Atomix 3.1.0-rc2Thu Sep 23 07:38:36 2021 +0000
[SDFAB-612] Cluster not ready when using recent tost master images
--
(cherry picked from commit ec0e942320ef27932b4173172055151015261d7c)
Case 1: Starting up
...
5 node(s) ONOS cluster -
...
PASS
Set up ONOS with 7 5 node(s) ONOS cluster
- 1.1 Constructing test variables - PASS
- 1.2 Apply cell to environment - PASS
- 1.3 Uninstalling Atomix - PASS
- 1.4 Uninstalling ONOS package - PASS
- 1.5 Starting Mininet - PASS
- 1.6 Creating ONOS package - PASS
- 1.7 Installing Atomix - PASS
- 1.8 Installing ONOS package - PASS
- 1.9 Set up ONOS secure SSH - PASS
- 1.10 Checking ONOS service - PASS
- 1.11 Starting ONOS CLI sessions - PASS
- 1.12 Checking ONOS nodes - PASS
- 1.13 Checking ONOS applications - PASS
- 1.14 Checking ONOS nodes - PASS
- 1.15 Activate apps defined in the params file - No Result
- 1.16 Set ONOS configurations - FAIL Failed to set config
- PASS
- 1.17 Check app ids - PASS
- 1.18 Set logging levels - PASS
...
- 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() - FAIL
- Set clear was incorrect
- PASS
- 17.18 Distributed Set addAll() - PASS
- 17.19 Distributed Set retain() - PASS FAIL
- Set retain was incorrect
- 17 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 - 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: Restart entire ONOS cluster with backed up state -
...
PASS
- 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
- 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 - FAIL
- Nodes check NOT successful
- PASS
Case 3: Adding host Intents - PASS
...
- 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 FAIL
- Set elements are incorrect
- 17.9 Distributed Set size - PASS FAIL
- Set sizes are incorrect
- 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() - FAIL Set clear was incorrect
- PASS
- 17.18 Distributed Set addAll() - PASS
- 17.19 Distributed Set retain() - PASS FAIL
- Set retain was incorrect
- 17 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 - 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
...
- 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 - FAIL Nodes check NOT successful
- 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 - FAIL Intents have not been installed correctly, pings failed.
- 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
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 13: Test Cleanup - PASS
- 13.1 Checking raft log size - PASS
- 13.2 Killing tcpdumps - No Result
- 13.3 Checking ONOS Logs for errors - No Result
- 13.4 Stopping Mininet - PASS