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/HAsanity_onos-1.14_20-builds_graph.jpg", alt="HAsanity", style="width:525px;height:350px;border:0"> |
commit b3e821d417eddc0c0345d7848a5e62ddd47ff5c3 756effd4a8f635d84c5f378513d351efd526c6e6 (HEAD -] onos-1.14, origin/onos-1.14)
Author: Carmelo Cascone Jian Li [carmelo@opennetworkingpyguni@gmail.orgcom]
AuthorDate: Fri Sep 7 1914 20:0653:26 07 2018 -0700+0900
Commit: Carmelo Cascone Jian Li [carmelo@opennetworkingpyguni@gmail.orgcom]
CommitDate: Fri Sat Sep 7 1915 02:4429:50 30 2018 -0700
Increase gRPC inbound msg size for P4Runtime client+0000
Fix: resolve a set of NPEs and WARNs caused by null instance port
Case 1: Constructing test variables and building ONOS package - 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 Compare switch roles from before failure - PASS
- 7.5 Get the intents from each controller - PASS
- 7.6 Check for consistency in Intents from each controller - PASS
- 7.7 Compare current intents with intents before the failure - PASS
- 7.8 Get the OF Table entries and compare to before component failure - PASS
- 7.9 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
...
- 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 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
...
- 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 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 11: Killing a switch to ensure it is discovered correctly - 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 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
...
- 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 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
...