Page History

...

commit c553c954c89a9d91eecf679a5719105ddab025fc 9ea8ecb5eb6ecd3f93ab89f4cc691e77ab860c78 (HEAD, origin/master, origin/HEAD, master)
Author: chengfan [chengfannature@gmailPriyanka B [priyanka.b@huawei.com]
AuthorDate: Fri Tue Jul 22 1526 09:4853:23 22 2016 +08000530
Commit: Gerrit Code Review [gerrit@onlab.usPriyankab-Huawei [priyanka.b@huawei.com]
CommitDate: Sun Tue Jul 24 0126 08:5619:44 51 2016 +0000

[ONOS-4946] fix bug: GetTunnelCount cast exception when getting the device property panel details in WEB GUIupdate command defect fix for cost type
--
(cherry picked from commit 7e3bfa4c3f96600a37182fd581d9df08026aa19e)

<iframe src="https://onos-jenkins.onlab.us/job/HAfullNetPartition/plot/Plot-HA/getPlot?index=1&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
• 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 3 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

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 Check Intent state - FAIL
• Intents are not all in INSTALLED state
• PASS
• 4.2 Ping across added host intents - FAIL
• Intents have not been installed correctly, pings failed.
• 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 - PASS

...

• 62.1 Deleteing firewall rules - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

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 - FAIL
• ONOS nodes have different views of hosts
• 8.3 Hosts information is correct - FAIL
• Host information is incorrect
• 8.4 Host attachment points to the network - PASS