Page History

...

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

commit 908cff4847cf48a62fdf7bb57d776ef165db29bc 7ce775a59e9e3853a9a2f71d7ddd070af7151af1 (HEAD -] master, origin/master, origin/HEAD)
Author: Thomas Vachuska Jian Li [tom@opennetworkingpyguni@gmail.orgcom]
AuthorDate: Tue Thu Oct 16 0818 07:2724:29 53 2018 -0700+0900
Commit: Thomas Vachuska Jian Li [tom@opennetworkingpyguni@gmail.orgcom]
CommitDate: Tue Wed Oct 16 0817 22:2753:29 2018 -0700
Fixing README.md file for github.51 2018 +0000

Fix: resolve a NPE caused by non-exist gateway at openstack subnet

Case 1: Constructing test variables and building ONOS package - PASS

...

• 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 5: Setting up and gathering data for current state -

...

FAIL

• 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 FAIL
• ONOS nodes have different views of switch roles
• 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 - PASS
• 5.16 Comparing ONOS topology to MN - PASS
• 5.17 Device information is correct - PASS
• 5.18 Links are correct - PASS
• 5.19 Hosts are correct - PASS

...

• 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 -

...

FAIL

• 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 FAIL
• ONOS nodes have different views of switch roles
• 7.4 Compare switch roles from before failure - PASS FAIL
• Mastership of some switches changed
• 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 FAIL
• Something went wrong with Leadership election

Case 104: Check connectivity - PASS

...