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-VM/lastSuccessfulBuild/artifact/HAfullNetPartition_onos-2.2_20-builds_graph.jpg", alt="HAfullNetPartition", style="width:525px;height:350px;border:0"> |
commit e80c15bc3580db128129cc170f152f1e8a09d8f2 8ee219fd7ea1e230c497ff00943c7c4007f2a827 (HEAD, origin/onos-2.2, onos-2.2)
Author: ONOS Jenkins User pierventre [jenkins@onlabpier@opennetworking.usorg]
AuthorDate: Mon Tue Sep 28 1715 12:2644:11 52 2020 +00000200
Commit: ONOS Jenkins User [jenkins@onlab.usPier Luigi Ventre [pier@opennetworking.org]
CommitDate: Mon Sep 28 17:26:11 Fri Oct 2 10:21:52 2020 +0000
Starting snapshot 2.2.6-SNAPSHOT
[AETHER-38] Moves T3 utils to ONOS utils
Case 1: Constructing test variables and building ONOS package - PASS
...
- 62.1 Deleteing firewall rules - PASS
- 62.2 Checking ONOS nodes - 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 - 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 19 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
...
- 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 FAIL
- ONOS nodes have different views of intents
- 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
- 7.8 Leadership Election is still functional - FAIL
- Something went wrong with Leadership election
- PASS
Case 4Case 4: Verify connectivity by sending traffic across Intents - FAIL
...
- 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 - 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 - FAIL
- ONOS shows 19 12 SCCs
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - FAIL
- Links are incorrect
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - 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 - 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 - FAIL
- ONOS shows 19 12 SCCs
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - FAIL
- Links are incorrect
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - 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 - FAIL
Compare topology objects between Mininet and ONOS
- 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 - 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 - FAIL
- ONOS nodes have different views of clusters
- PASS
- 8.6 There is only one SCC - PASS FAIL
- ONOS shows 12 SCCs
- 8.7 Device information is correct - FAIL
- Device information is incorrect
- PASS
- 8.8 Links are correct - PASS FAIL
- Links are incorrect
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - PASS
...
- 4.1 Check Intent state - FAIL
- Intents are not all in INSTALLED state
- 4.2 Ping across added host 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 - 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 - FAIL ONOS nodes have different views of clusters
- PASS
- 8.6 There is only one SCC - PASS FAIL
- ONOS shows 12 SCCs
- 8.7 Device information is correct - FAIL
- Device information is incorrect
- PASS
- 8.8 Links are correct - PASS FAIL
- Links are incorrect
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - 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 FAIL
- Intents are not all in INSTALLED state
- 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
...