...
HTML |
---|
<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 ec1a420030d2ecab77909056a34aee50f808f72f a25251cdf5a6ad61cf23f8d5b10ac7df375c891a (HEAD -] master, origin/master, origin/HEAD)
Author: ghj0504520 [ghj0504520.cywjjy@gmailseunghyeon lee [leesh@telcoware.com]
AuthorDate: Mon Fri Oct 22 26 10:5049:41 34 2018 -0700+0900
Commit: Carmelo Cascone Jian Li [carmelo@opennetworkingpyguni@gmail.orgcom]
CommitDate: Wed Fri Oct 24 1926 07:5933:22 51 2018 +0000
[ONOS-7810 calculate cookie field when pipeconf registered7731] Removed redundant functions in GUI of openstackVtapApp
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 -
...
PASS
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 - FAIL
- Nodes check NOT successful
- PASS
Case 3: Adding host Intents -
...
PASS
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 - FAIL 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 - FAIL ONOS nodes have different views of switch roles
- PASS
- 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 -
...
PASS
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 - 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
...
- 9.1 Kill Link between s28 and s3 - PASS
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 - 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 - FAIL
- Nodes check NOT successful
- 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 - 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 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 -
...
PASS
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 - FAIL Nodes check NOT successful
- 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 - PASS
- 4.2 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- 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.
- PASS
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 -
...
PASS
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 - FAIL Nodes check NOT successful
- 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 - 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 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 -
...
PASS
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 - FAIL
- Nodes check NOT successful
- 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 - 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 13: Test Cleanup - PASS
...