Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
...
| HTML |
|---|
<img src="https://jenkins.onosproject.org/view/QA/job/postjob-Fabric/lastSuccessfulBuild/artifact/HAbackupRecover_master_20-builds_graph.jpg", alt="HAbackupRecover", style="width:525px;height:350px;border:0"> |
commit 8b5599b802c1aa3f43e5f01564853c946439c77a 6777d5338605a5f46053fa5677dd19a32d0975fa (HEAD -] master, origin/master, origin/HEAD)
Author: Jian Li Jonghwan Hyun [pyguni@gmailjonghwan@opennetworking.comorg]
AuthorDate: Mon Sun Nov 19 18 20:4550:46 16 2018 +0900
Commit: Thomas Vachuska Carmelo Cascone [tom@opennetworkingcarmelo@opennetworking.org]
CommitDate: Mon Wed Nov 19 21 02:5138:13 48 2018 +0000
Fix: enforce to synchronize all flow rules in case sync failures
Implement INT Telemetry Reporting functionality
Case 1: Starting up 7 node(s) ONOS cluster - PASS
...
- 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
Case 104: Check connectivity -
...
FAIL
- 104.1 Ping 1 Ping between all hosts - FAIL
- Failed to ping between all hosts
Case 8: Compare ONOS Topology view to Mininet topology - PASS
...
- 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
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
- 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 FAIL
- Something went wrong with Leadership election
Case 104: Check connectivity -
...
PASS
- 104.1 Ping between all hosts - FAIL Failed to ping between all hosts
- PASS
Case 15: Check that Leadership Election is still functional - PASS
...
- 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
Case 104: Check connectivity -
...
PASS
- 104.1 Ping between all hosts - FAIL
- Failed to ping between all hosts
- PASS
Case 10: Restore a link to ensure that Link Discovery is working properly - PASS
...
- 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
Case 104: Check connectivity -
...
PASS
- 104.1 Ping between all hosts - FAIL Failed to ping between all hosts
- PASS
Case 13: Test Cleanup - PASS
...