<img src="https://jenkins.onosproject.org/view/QA/job/postjob-Fabric4/lastSuccessfulBuild/artifact/HAbackupRecover_master_20-builds_graph.jpg", alt="HAbackupRecover", style="width:525px;height:350px;border:0">

commit a828719294709152f3a7704ff851e00360ab1b4e (HEAD -] master, origin/master, origin/HEAD)
Author: Niraj Dubey [niraj.d@samsung.com]
AuthorDate: Tue Mar 23 19:54:17 2021 +0530
Commit: Thomas Vachuska [tom@opennetworking.org]
CommitDate: Fri Aug 27 16:06:48 2021 +0000

BGP Monitoring in ONOS.

Case 1: Starting up 3 node(s) ONOS cluster - PASS

Set up ONOS with 3 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 Creating ONOS package - PASS
• 1.6 Installing Atomix - PASS
• 1.7 Installing ONOS package - PASS
• 1.8 Set up ONOS secure SSH - PASS
• 1.9 Checking ONOS service - PASS
• 1.10 Starting ONOS CLI sessions - PASS
• 1.11 Checking ONOS nodes - PASS
• 1.12 Checking ONOS applications - PASS
• 1.13 Checking ONOS nodes - PASS
• 1.14 Activate apps defined in the params file - No Result
• 1.15 Set ONOS configurations - PASS
• 1.16 Check app ids - PASS
• 1.17 Set logging levels - PASS

Case 102: Starting Mininet Topology - FAIL

• 102.1 Pushing Network config - PASS
• 102.2 Check Network config - FAIL
• Net Cfg not correctly set
• 102.3 Start Mininet topology - 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 - 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 - FAIL
• ONOS nodes have different views of clusters
• 8.6 There is only one SCC - FAIL
• ONOS shows 7 SCCs
• 8.7 Device information is correct - 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 104: Check connectivity - FAIL

• 104.1 Ping between all hosts - FAIL
• Failed to ping between all hosts

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 - 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 - FAIL
• ONOS nodes have different views of clusters
• 8.6 There is only one SCC - FAIL
• ONOS shows 7 SCCs
• 8.7 Device information is correct - 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 5: Setting up and gathering data for current state - FAIL

• 5.1 Check that each switch has a master - FAIL
• Some devices don't have a master assigned
• 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 - PASS
• 5.14 Cluster view is consistent across ONOS nodes - PASS
• 5.15 Cluster view correct across ONOS nodes - FAIL
• ONOS shows 0 SCCs
• 5.16 Comparing ONOS topology to MN - PASS
• 5.17 Device information is correct - FAIL
• Device information is incorrect
• 5.18 Links are correct - FAIL
• Links are incorrect
• 5.19 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 Active node was elected leader? - 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 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 - 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
• 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 - 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 - 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 - FAIL
• ONOS shows 0 SCCs
• 8.7 Device information is correct - 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 7: Running ONOS Constant State Tests - FAIL

• 7.1 Check that each switch has a master - FAIL
• Some devices don't have a master assigned
• 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 104: Check connectivity - FAIL

• 104.1 Ping between all hosts - FAIL
• Failed to ping between all hosts

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 - 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
• 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 9: Turn off a link to ensure that Link Discovery is working properly - PASS

• 9.1 Kill Link between spine102 and leaf1 - 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 - 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 - FAIL
• ONOS shows 0 SCCs
• 8.7 Device information is correct - 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 104: Check connectivity - FAIL

• 104.1 Ping between all hosts - FAIL
• Failed to ping between all hosts

Case 10: Restore a link to ensure that Link Discovery is working properly - PASS

• 10.1 Bring link between spine102 and leaf1 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 - 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 - FAIL
• ONOS shows 0 SCCs
• 8.7 Device information is correct - 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 104: Check connectivity - FAIL

• 104.1 Ping between all hosts - FAIL
• Failed to ping between all hosts

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