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_master_20-builds_graph.jpg", alt="HAfullNetPartition", style="width:525px;height:350px;border:0"> |
commit 8479dd1eb35e69448c50acd20fcf9dbb02d74c4f d14f1a3f22a212ae2a0f5e97fa416264a1c5903d (HEAD, origin/master, origin/HEAD, master)
Author: Andrea Campanella Yi Tseng [andrea@opennetworkingyi@opennetworking.org]
AuthorDate: Mon Tue Oct 13 19 10:4415:15 12 2020 +0200-0700
Commit: Andrea Campanella Yi Tseng [andrea@opennetworkingyi@opennetworking.org]
CommitDate: Mon Fri Oct 19 1423 01:1509:37 2020 +0000
Escaping regex reserved chars
--
(cherry picked from commit 84e2ecffb63420ac8b8221bbe9cb353c0176a5cd)40 2020 -0700
Support install IntIntents to device with postcard mode
Case 1: Constructing test variables and building ONOS package - 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 24 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 7: Running ONOS Constant State Tests - FAIL
- 7.1 Check that each switch has a master - FAIL
- Some devices don't have a master assigned
- 7.2 Read device roles from ONOS - FAIL
- Error in reading roles from ONOS
- 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 - FAIL
- ONOS nodes have different views of intents
- 7.6 Compare current intents with intents before the failure - FAIL
- The Intents changed during failure
- 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
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 - 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 - FAIL
- Intents have not been installed correctly, pings failed.
Case 15: Check that Leadership Election is still functional - FAIL
- 15.1 Run for election on each node - FAIL
- At least one node failed to run for leadership
- Skipping the rest of this case.