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-Fabric3/lastSuccessfulBuild/artifact/HAfullNetPartition_onos-2.2_20-builds_graph.jpg", alt="HAfullNetPartition", style="width:525px;height:350px;border:0"> |
commit b5ade98a2d189ade5c4520c96d65b31add6050fe 2d9ca233f0205c67d97feff7cff295d4108d7a1c (HEAD -] onos-2.2, origin/onos-2.2)
Author: Davide Scano [d.scano89@gmail.comONOS Jenkins User [jenkins@onlab.us]
AuthorDate: Wed Jun 3 21:47:13 2020 +0200Fri Aug 14 06:09:35 2020 +0000
Commit: Sean Condon [sean@opennetworking.orgONOS Jenkins User [jenkins@onlab.us]
CommitDate: Fri Aug 7 1114 06:2309:59 35 2020 +0100
INT app gui20000
Starting snapshot 2.2.5-SNAPSHOT
Case 1: Constructing test variables and building ONOS package - 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 between all hosts - PASS FAIL
- Failed to ping between all hosts
Case 5: Setting up and gathering data for current state - 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 from each controller - PASS
- 7.5 Check for consistency in Intents from each controller - PASS
- 7.6 Compare current intents with intents before the failure - PASS
- 7.7 Get the OF Table entries and compare to before component failure - PASS
- 7.8 Leadership Election is still functional - PASS
Case 104: Check connectivity -
...
FAIL
- 104.1 Ping between all hosts - PASS FAIL
- Failed to ping between all hosts
Case 15: Check that Leadership Election is still functional - 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
- 7.4 Get the intents from each controller - PASS
- 7.5 Check for consistency in Intents from each controller - PASS
- 7.6 Compare current intents with intents before the failure - PASS
- 7.7 Get the OF Table entries and compare to before component failure - PASS failure - FAIL
- Changes were found in the flow tables
- 7.8 Leadership Election is still functional - PASS FAIL
- Something went wrong with Leadership election
Case 104: Check connectivity -
...
FAIL
- 104.1 Ping between all hosts - PASS FAIL
- Failed to ping between all hosts
Case 15: Check that Leadership Election is still functional - PASS
...
- 9.1 Kill Link between spine102 and leaf1 - 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 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 - PASS FAIL
- ONOS shows 6 SCCs
- 8.7 Device information is correct - PASS
- 8.8 8 Links are correct - FAIL
- Links are
- incorrect
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - PASS
Case 104: Check connectivity -
...
FAIL
- 104.1 Ping between all hosts - PASS FAIL
- Failed to ping between all hosts
Case 10: Restore a link to ensure that Link Discovery is working properly - PASS
...
- 10.1 Bring link between spine102 and leaf1 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 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 - PASS FAIL
- ONOS shows 6 SCCs
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - PASS FAIL
- Links are incorrect
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - PASS
Case 104: Check connectivity -
...
FAIL
- 104.1 Ping between all hosts - PASS FAIL
- Failed to ping between all hosts
Case 13: Test Cleanup - PASS
...