Page History

...

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

commit 9ef930aa75aacbd6c7f9af0bc7ede872b6402ded 924f01f31f8302a8680a6a16f1e43d56e469bd4f (HEAD -] master, origin/master, origin/HEAD)
Author: Andrea Campanella [andrea@opennetworking.orgAnurag Chadha [anurag.chadha@hsc.com]
AuthorDate: Fri Nov 6 21:41:01 Dec 4 19:48:56 2020 +01000530
Commit: Andrea Campanella Thomas Vachuska [andrea@opennetworkingtom@opennetworking.org]
CommitDate: Wed Nov 11 19:06:10 2020 +0000
Offload OF Port Status message processing to a single thread executor.
--
(cherry picked from commit dad65ac5a058242326fe91fbe47e65fa9c5a3583)Fri Jan 8 00:54:25 2021 +0000

[ONOS-8129] Bug fixed for duplicate events when netconf device goes down along with some fixes for NPE in NetconfControllerImpl

Case 1: Constructing test variables and building ONOS package -

...

PASS

For loading from params file, and pull and build the latest ONOS package

• 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 - FAIL
Not all ONOS apps are activated
• 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

...

• 61.1 Checking ONOS Logs for errors - No Result
• 61.2 Partitioning ONOS nodes - PASS
• 61.3 Sleeping 60 seconds - No Result

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 - 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 - PASS
• 8.10 Checking ONOS nodes - PASS

...

• 62.1 Deleteing firewall rules - PASS
• 62.2 Checking ONOS nodes - 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 - 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
• PASS
• 8.6 There is only one SCC - PASS
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - FAIL
Links are incorrect
• PASS
• 8.9 Hosts are correct - 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 Compare current intents with intents before the failure - PASS
• 7.7 Get the OF Table entries and compare to before component failure - FAIL
• Changes were found in the flow tables
• 7.8 Leadership Election is still functional - FAIL
Something went wrong with Leadership election
• PASS

Case 104: Check connectivity - FAIL

...

• 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 - FAIL
ONOS nodes have different views of clusters
• PASS
• 8.6 There is only one SCC - FAIL
• ONOS shows 4 6 SCCs
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - FAIL
• Links are incorrect
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - 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 - FAIL
ONOS nodes have different views of clusters
• PASS
• 8.6 There is only one SCC - FAIL
• ONOS shows 3 6 SCCs
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - FAIL
• Links are incorrect
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - PASS

...