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.
...
commit 79d6a83e2b2d3dd5b725a0feba52aa5e4e82deec 0b33c089054d0077cae534655ebf9f367975f237 (HEAD, origin/master, origin/HEAD, master)
Author: sangho [sangho@onlab.ussivachidambaram subramanian [sisubram@partner.ciena.com]
AuthorDate: Tue May 2 14:53:46 2017 +0900Thu Apr 6 13:26:44 2017 +0530
Commit: Sangho Shin Ray Milkey [sangho@onlabray@onlab.us]
CommitDate: Tue Wed May 16 0617 02:1726:29 20 2017 +0000
Reduces the port number range for snat to reduce snat handler initialization time.
[ONOS-6239] Flows are missing after mastership change if 'backupEnabled' is set to false
--
(cherry picked from commit 75830f01d96bde802dfaf7d88317cf253fc934b7)
| HTML |
|---|
<iframe src="https://onos-jenkins.onlab.us/job/HAswapNodes/plot/Plot-HA/getPlot?index=2&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe> |
...
- 3.1 Install reactive forwarding app - PASS
- 3.2 Check app ids - FAIL
- Something is wrong with app Ids
- PASS
- 3.3 Discovering Hosts( Via pingall for now ) - FAIL
- Reactive Pingall failed, one or more ping pairs failed
- PASS
- 3.4 Uninstall reactive forwarding app - PASS
- 3.5 Check app ids - FAIL
- PASS
- 3.6 Add host intents via cli - PASS
- 3.7 Intent Anti-Entropy dispersion - FAIL
Case 7: Running ONOS Constant State Tests -
...
No Result
- 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 and compare across all nodes - 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 scaling - FAIL
- The Intents changed during scaling
- 7.7 Get the OF Table entries and compare to before component scaling - 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 - PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
Case 15: Check that Leadership Election is still functional - FAIL
- 15.1 Run for election on each node - PASS
- 15.2 Check that each node shows the same leader and candidates - FAIL
- Nodes have different leaderboards
- 15.3 Find current leader and withdraw - FAIL
- Node was not withdrawn from election
- 15.4 Check that a new node was elected leader - FAIL
- Something went wrong with Leadership election
- 15.5 Check that that new leader was the candidate of old leader - FAIL
- Incorrect Candidate Elected
- 15.6 Run for election on old leader( just so everyone is in the hat ) - FAIL
- App failed to run for election
- 15.7 Check that oldLeader is a candidate, and leader if only 1 node - FAIL
- Something went wrong with Leadership election after the old leader re-ran for election Error in reading intents from ONOS