Page History

...

commit e4a60d5dac3630731e8e3ea8cbbb83e1d3f9cf4e 886d918be34a31a33d14b6eb4470ea5060857c31 (HEAD, origin/onos-1.5, onos-1.5)
Author: Varun Sharma Prince Pereira [varunsha@partnerprpereir@partner.ciena.com]
AuthorDate: Tue Jul 12 08:32:27 Jun 14 16:01:59 2016 +0530
Commit: Varun Sharma [varunsha@partner.ciena.comGerrit Code Review [gerrit@onlab.us]
CommitDate: Tue Thu Jul 12 0921 01:5245:47 28 2016 +0530
ONOS-4835 0000

Backporting the fix from onos-1.6 (change-id : I82e1e0e55bbc017d6c0cce7d9a6af7a578d7196e ) for ONOS-4641 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>

...

• 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 - FAIL
• ONOS shows 3 13 SCCs
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - PASS FAIL
• Links are incorrect
• 8.9 Checking ONOS nodes - 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 - FAIL
• Something went wrong with Leadership election
• PASS
• 15.5 Check that that new leader was the candidate of old leader - FAIL
• Incorrect Candidate Elected
• 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 - PASS

...

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

Case 7: Running ONOS Constant State Tests -

...

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
• PASS
• 7.6 Compare current intents with intents before the failure - FAIL
• The Intents changed during failure
• PASS
• 7.7 Get the OF Table entries and compare to before component failure - FAIL
• Changes were found in the flow tables
• PASS
• 7.8 Leadership Election is still functional - 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 Ping across added host intents - FAIL
Intents have not been installed correctly, pings failed.
• PASS
• 4.2 Check Intent state - FAIL
Intents are not all in INSTALLED state
• 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 15: Check that Leadership Election is still functional - FAIL

...

• 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 - PASS
• 8.7 Device information is correct - FAIL
• Device information is incorrect
• 8.8 Links are correct - FAIL
• Links are incorrect
• PASS
• 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 - FAIL
• Intents have not been installed correctly, pings failed.
• 4.2 Check Intent state - FAIL
• Intents are not all in INSTALLED state
• PASS
• 4. 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL
• Intents have not been installed correctly, pings failed.

...

• 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 - PASS
• 8.7 Device information is correct - FAIL
• Device information is incorrect
• 8.8 Links are correct - FAIL
Links are incorrect
• PASS
• 8.9 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 Ping across added host intents - FAIL
Intents have not been installed correctly, pings failed.
• PASS
• 4.2 Check Intent state - FAIL
• Intents are not all in INSTALLED state
• 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 11: Killing a switch to ensure it is discovered correctly - PASS

...

• 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 - PASS
• 8.7 Device information is correct - FAIL
• Device information is incorrect
• 8.8 Links are correct - FAIL
• Links are incorrect
• PASS
• 8. 8.9 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 Ping across added host intents - FAIL
Intents have not been installed correctly, pings failed.
• PASS
• 4.2 Check Intent state - FAIL
• Intents are not all in INSTALLED state
• 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 12: Adding a switch to ensure it is discovered correctly - PASS

...

• 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 - PASS
• 8.7 Device information is correct - FAIL
• Device information is incorrect
• 8.8 Links are correct - FAIL
• Links are incorrect
• PASS
• 8.9 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 Ping across added host intents - FAIL
• Intents have not been installed correctly, pings failed.
• PASS
• 4.2 Check Intent state - FAIL
• Intents are not all in INSTALLED state
• 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 13: Test Cleanup - PASS

...