Page History

...

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

commit 55f80b6a232df2cd673b82c9d5c42b013aa07876 ec1a420030d2ecab77909056a34aee50f808f72f (HEAD -] master, origin/master, origin/HEAD)
Author: 柯志勇10068695 ghj0504520 [keghj0504520.zhiyong@ztecywjjy@gmail.com.cn]
AuthorDate: Thu Mon Oct 11 1722 10:2850:31 41 2018 +0800-0700
Commit: Ray Milkey Carmelo Cascone [ray@opennetworkingcarmelo@opennetworking.org]
CommitDate: Fri Wed Oct 24 19 05:5459:58 22 2018 +0000
The result of dis.getMessageDigest().digest() must be returned here. Otherwise, this method will lose its meaning.
ONOS-7810 calculate cookie field when pipeconf registered

Case 1: Starting up 7 node(s) ONOS cluster - PASS

...

• 6.1 Backup ONOS data - PASS
• 6.2 Checking ONOS Logs for errors - No Result
• 6.3 Uninstalling ONOS package - PASS
• 6.4 Installing ONOS package - PASS
• 6.5 Restore ONOS data - PASS
• 6.6 Restart ONOS nodes - No Result
• 6.7 Set up ONOS secure SSH - PASS
• 6.8 Checking ONOS service - PASS
• 6.9 Starting ONOS CLI sessions - 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
• 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 FAIL
• Nodes check NOT successful

Case 3: Adding host Intents -

...

FAIL

Discover hosts by using pingall then assign predetermined host-to-host intents. After installation, check that the intent is distributed to all nodes and the state is INSTALLED

• 3.1 Install reactive forwarding app - PASS
• 3.2 Check app ids - PASS
• 3.3 Discovering Hosts( Via pingall for now ) - PASS
• 3.4 Uninstall reactive forwarding app - PASS
• 3.5 Check app ids - PASS
• 3.6 Add host intents via cli - PASS
• 3.7 Intent Anti-Entropy dispersion - PASS FAIL

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 Get the intents from each controller - PASS
• 7.5 Check for consistency in Intents from each controller - PASS
• 7.6 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 Check Intent state - PASS
• 4.2 Ping across added host intents - PASS intents - FAIL
• Intents have not been installed correctly, pings failed.
• 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 15: Check that Leadership Election is still functional - PASS

...

• 9.1 Kill Link between s28 and s3 - 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
• 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 FAIL
• Nodes check NOT successful

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 Check Intent state - PASS
• 4.2 Ping across added host intents - PASS FAIL
• Intents have not been installed correctly, pings failed.
• 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 s28 and s3 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 - 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 FAIL
• Nodes check NOT successful

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 Check Intent state - PASS
• 4.2 Ping across added host intents - PASS FAIL
• Intents have not been installed correctly, pings failed.
• 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 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 - 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 FAIL
• Nodes check NOT successful

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 Check Intent state - PASS
• 4.2 Ping across added host intents - PASS intents - FAIL
• Intents have not been installed correctly, pings failed.
• 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 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 - 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 FAIL
• Nodes check NOT successful

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

...