Page History

...

commit 0cf9e346d693db75136e1069afe348d2272cef68 ca8b51e7f08d497fb947ff545be187b4f4a14fef (HEAD, origin/onos-1.5, onos-1.5)
Author: Charles Chan [rascov@gmailVarun Sharma [varunsha@partner.ciena.com]
AuthorDate: Thu Fri Jun 16 2017 17:4311:19 02 2016 -0700+0530
Commit: Gerrit Code Review [gerrit@onlab.usVarun Sharma [varunsha@partner.ciena.com]
CommitDate: Fri Sat Jun 17 1718 16:5926:58 27 2016 +0000
Backport bugfix for NPE to onos-1.5
--
(from commit 04b1fe9adab1382e89a743174b40505f900cd6b9)
Change-Id: Ie2af821e232bc8a1c9d6828c464bf3e54ad8cd110530

ONOS-4721 fix

<iframe src="https://onos-jenkins.onlab.us/job/HAfullNetPartition/plot/Plot-HA/getPlot?index=0&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

...

• 61.1 Checking ONOS Logs for errors - No Result
• 61.2 Partitioning ONOS nodes - 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 - PASS 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 - PASS FAIL
• ONOS shows 3 SCCs
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - PASS FAIL
• Links are incorrect
• 8.9 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 and compare across all nodes - PASS
• 7.5 Check for consistency in Intents from each controller - FAIL
• ONOS nodes have different views of intents
• 7.6 Compare current intents with intents before the failure - FAIL
• The Intents changed during failure
• 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 - PASS

Case 4: Verify connectivity by sending traffic across Intents -

...

FAIL

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Ping across added host intents - PASS FAIL
• Intents have not been installed correctly, pings failed.
• 4.2 Check Intent state - PASS
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - PASS again - FAIL
• Intents have not been installed correctly, pings failed.

Case 15: Check that Leadership Election is still functional - FAIL

...

• 62.1 Deleteing firewall rules - 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 FAIL
• ONOS nodes have different views of hosts
• 8.3 Hosts information is correct - PASS FAIL
• Host information is incorrect
• 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 3 SCCs
• PASS
• 8.7 Device information is correct - FAIL
• Device information is incorrect
• 8.8 Links are correct - PASS FAIL
• Links are incorrect
• 8.9 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 and compare across all nodes - PASS
• 7.5 Check for consistency in Intents from each controller - FAIL
• ONOS nodes have different views of intents
• 7.6 Compare current intents with intents before the failure - FAIL
• The Intents changed during failure
• 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 - PASS

Case 4: Verify connectivity by sending traffic across Intents - FAIL

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Ping across added host intents - FAIL
• Intents have not been installed correctly, pings failed.
• 4.2 Check Intent state - PASS FAIL
• Intents are not all in INSTALLED state
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - PASS again - FAIL
• Intents have not been installed correctly, pings failed.

Case 15: Check that Leadership Election is still functional - FAIL

...

• 9.1 Kill Link between s3 and s28 - 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 4 SCCs
• PASS
• 8.7 Device information is correct - FAIL
• Device information is incorrect
• 8.8 Links are correct - PASS FAIL
• Links are incorrect
• 8.9 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sending traffic across Intents -

...

FAIL

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Ping across added host intents - PASS FAIL
• Intents have not been installed correctly, pings failed.
• 4.2 Check Intent state - PASS FAIL
• Intents are not all in INSTALLED state
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - PASS FAIL
• Intents have not been installed correctly, pings failed.

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

...

• 10.1 Bring link between s3 and s28 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
• 8.6 There is only one SCC - FAIL
• ONOS shows 3 SCCs
• PASS
• 8.7 Device information is correct - FAIL
• Device information is incorrect
• 8.8 Links are correct - PASS FAIL
• Links are incorrect
• 8.9 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sending traffic across Intents -

...

FAIL

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Ping across added host intents - PASS FAIL
• Intents have not been installed correctly, pings failed.
• 4.2 Check Intent state - PASS FAIL
• Intents are not all in INSTALLED state
• 4.3 Check leadership of topics - PASS
• 4.4 .4 Wait a minute then ping again - PASS Wait a minute then ping again - FAIL
• Intents have not been installed correctly, pings failed.

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 - 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 2 SCCs
• PASS
• 8.7 Device information is correct - FAIL
• Device information is incorrect
• 8.8 Links are correct - PASS FAIL
• Links are incorrect
• 8.9 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sending traffic across Intents -

...

FAIL

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Ping across added host intents - PASS FAIL
• Intents have not been installed correctly, pings failed.
• 4.2 Check Intent state - PASS FAIL
• Intents are not all in INSTALLED state
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - PASS again - FAIL
• Intents have not been installed correctly, pings failed.

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 - 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 3 SCCs
• PASS
• 8.7 Device information is correct - FAIL
• Device information is incorrect
• 8.8 Links are correct - PASS FAIL
• Links are incorrect
• 8.9 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sending traffic across Intents -

...

FAIL

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Ping across added host intents - PASS FAIL
• Intents have not been installed correctly, pings failed.
• 4.2 Check Intent state - PASS FAIL
• Intents are not all in INSTALLED state
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - PASS FAIL
• Intents have not been installed correctly, pings failed.

Case 13: Test Cleanup - PASS

...