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 b222e7475d46cddf3c2eb9f395786796b13e7f1c 978223fab120d080083edd1074f0d0d780ef89ee (HEAD, origin/onos-1.5, onos-1.5)
Author: Brian O'Connor [bocon@onlab.uslishuai [lishuai12@huawei.com]
AuthorDate: Wed Apr 20 22:39:44 2016 -0700
Commit: Brian O'Connor [bocon@onlabMay 4 17:00:16 2016 +0800
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Wed Apr 20 22:39:44 2016 -0700
Starting snapshot 1.5.2-SNAPSHOTMon May 9 09:15:21 2016 +0000
[ONOS-4502]Fix the bug about the different tenant and the same
HTML |
---|
<iframe src="https://onos-jenkins.onlab.us/job/HAfullNetPartition/plot/Plot-HA/getPlot?index=0&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe> |
...
- 17.1 Increment then get a default counter on each node - PASS
- 17.2 Get then Increment a default counter on each node - PASS
- 17.3 Counters we added have the correct values - PASS
- 17.4 Add -8 to then get a default counter on each node - PASS
- 17.5 Add 5 to then get a default counter on each node - PASS
- 17.6 Get then add 5 to a default counter on each node - PASS
- 17.7 Counters we added have the correct values - PASS
- 17.8 Increment and get an in-memory counter on each node - PASS
- 17.9 Get then Increment a in-memory counter on each node - PASS
- 17.10 Counters we added have the correct values - PASS
- 17.11 Add -8 to then get a in-memory counter on each node - PASS
- 17.12 Add 5 to then get a in-memory counter on each node - PASS
- 17.13 Get then add 5 to a in-memory counter on each node - PASS
- 17.14 Counters we added have the correct values - PASS
- 17.15 Check counters are consistant across nodes - PASS
- 17.16 Counters we added have the correct values - PASS
- 17.17 Distributed Set get - PASS
- 17.18 Distributed Set size - PASS
- 17.19 Distributed Set add() - PASS
- 17.20 Distributed Set addAll() - FAIL
- Set addAll was incorrect
- PASS
- 17.21 Distributed Set contains() - PASS
- 17.22 Distributed Set containsAll() - PASS
- 17.23 Distributed Set remove() - PASS
- 17.24 Distributed Set removeAll() - FAIL
- Set removeAll was incorrect
- PASS
- 17.25 Distributed Set addAll() - FAIL
Set addAll
was incorrect - () - PASS
- 17.26 Distributed Set clear() - FAIL
- PASS
- 17.27 Distributed Set addAll() - FAIL
- Set addAll was incorrect
- PASS
- 17.28 Distributed Set retain() - PASS
- 17.29 Partitioned Transactional maps put - PASS
- 17.30 Partitioned Transactional maps get - PASS
- 17.31 In-memory Transactional maps put - PASS
- 17.32 In-Memory Transactional maps get - FAIL
- In-Memory Transactional Map values incorrect
...
- 4.1 Ping across added host intents - PASS
FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - FAIL
- Intents are not all in INSTALLED state
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - FAIL
- Intents have not been installed correctly, pings failed.
...
- 15.1 Run for election on each node - PASS
- 15.2 Check that each node shows the same leader and candidates - PASS
- 15.3 Find current leader and withdraw - PASS
- 15.4 Check that a new node was elected leader - PASS
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 ) - PASS
- 15.7 Check that oldLeader is a candidate, and leader if only 1 node - PASS
...
- 17.1 Increment then get a default counter on each node - PASS
- 17.2 Get then Increment a default counter on each node - PASS
- 17.3 Counters we added have the correct values - PASS
- 17.4 Add -8 to then get a default counter on each node - PASS
- 17.5 Add 5 to then get a default counter on each node - PASS
- 17.6 Get then add 5 to a default counter on each node - PASS
- 17.7 Counters we added have the correct values - PASS
- 17.8 Increment and get an in-memory counter on each node - PASS
- 17.9 Get then Increment a in-memory counter on each node - PASS
- 17.10 Counters we added have the correct values - PASS
- 17.11 Add -8 to then get a in-memory counter on each node - PASS
- 17.12 Add 5 to then get a in-memory counter on each node - PASS
- 17.13 Get then add 5 to a in-memory counter on each node - PASS
- 17.14 Counters we added have the correct values - PASS
- 17.15 Check counters are consistant across nodes - PASS
- 17.16 Counters we added have the correct values - PASS
- 17.17 Distributed Set get - PASS
- 17.18 Distributed Set size - PASS
- 17.19 Distributed Set add() - PASS
- 17.20 Distributed Set addAll() - PASS
- 17.21 Distributed Set contains() - PASS
- 17.22 Distributed Set containsAll() - PASS
- 17.23 Distributed Set remove() - PASS
- 17.24 Distributed Set removeAll() - PASS
- 17.25 Distributed Set addAll() - FAIL
- PASS
- 17.26 Distributed Set clear() - PASS
- 17.27 Distributed Set addAll() - FAIL
- PASS
- 17.28 Distributed Set retain() - PASS
- 17.29 Partitioned Transactional maps put - PASS
- 17.30 Partitioned Transactional maps get - PASS
- 17.31 In-memory Transactional maps put - PASS
- 17.32 In-Memory Transactional maps get - FAIL
- In-Memory Transactional Map values incorrect
...
- 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 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 Ping across added host intents - PASS
FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS
- 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
...
- 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 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 Ping across added host intents - PASS
FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS
- 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
...