...
commit bfa7f774a30789ae2db8418365796d5c978a1393 c97aa6110e76737169fc409ebdf763576ed6bd94 (HEAD, origin/master, origin/HEAD, master)
Author: Brian O'Connor [bocon@onlabThomas Vachuska [tom@onlab.us]
AuthorDate: Mon Tue Jun 22 2023 16:0400:20 18 2015 -04000700
Commit: Brian O'Connor [bocon@onlabGerrit Code Review [gerrit@onlab.us]
CommitDate: Mon Tue Jun 22 2023 23:0439:20 49 2015 -0400
Removing lxc cell due to conflicts+0000
ONOS-1793 Moved trivial stores to onos-core-common/src/test; onos-core-trivial is no longer.
HTML |
---|
<iframe src="https://onos-jenkins.onlab.us/job/HAClusterRestart/plot/Plot-HA/getPlot?index=0&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 - PASS
- 3.3 Discovering Hosts( Via pingall for now ) - FAIL
- Reactive Pingall failed, one or more ping pairs failed
- 3.4 Uninstall reactive forwarding app - PASS
- 3.5 Check app ids - PASS
- 3.6 Add host intents via cli - PASS
- 3.7 Intent Anti-Entropy dispersion - FAIL
- PASS
Case 7: Running ONOS Constant State Tests - FAIL
...
- 9.1 Kill Link between s3 and s28 - PASS
Case 8: Compare ONOS Topology view to Mininet topology -
...
PASS
Compare topology objects between Mininet and ONOS
- 8.1 Create TestONTopology object - PASS
- 8.2 Comparing ONOS topology to MN - No Result
- 8.3 Collecting topology information from ONOS - PASS
- 8.4 Hosts view is consistent across all ONOS nodes - PASS
- 8.5 Hosts information is correct - PASS
- 8.6 Host attachment points to the network - FAIL
- PASS
- 8.7 Clusters view is consistent across all ONOS nodes - PASS
- 8.8 There is only one SCC - PASS
- 8.9 Device information is correct - PASS
- 8.10 Port information is correct - PASS
- 8.11 Links are correct - PASS
- 8.12 Checking ONOS nodes - PASS
...
- 4.1 Ping across added host intents - 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 - FAIL
- PASS
Case 10: Restore a link to ensure that Link Discovery is working properly - PASS
...
- 10.1 Bring link between s3 and s28 back up - PASS
Case 8: Compare ONOS Topology view to Mininet topology -
...
PASS
Compare topology objects between Mininet and ONOS
- 8.1 Create TestONTopology object - PASS
- 8.2 Comparing ONOS topology to MN - No Result
- 8.3 Collecting topology information from ONOS - PASS
- 8.4 Hosts view is consistent across all ONOS nodes - PASS
- 8.5 Hosts information is correct - PASS
- 8.6 Host attachment points to the network - FAIL
- ONOS did not correctly attach hosts to the network
- PASS
- 8.7 Clusters view is consistent across all ONOS nodes - PASS
- 8.8 There is only one SCC - PASS
- 8.9 Device information is correct - PASS
- 8.10 Port information is correct - PASS
- 8.11 Links are correct - PASS
- 8.12 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sendind traffic across Intents -
...
PASS
Ping across added host intents to check functionality and check the state of the intent
- 4.1 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- PASS
- 4.2 Check Intent state - PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - FAIL
- - 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 -
...
PASS
Compare topology objects between Mininet and ONOS
- 8.1 Create TestONTopology object - PASS
- 8.2 Comparing ONOS topology to MN - No Result
- 8.3 Collecting topology information from ONOS - PASS
- 8.4 Hosts view is consistent across all ONOS nodes - PASS
- 8.5 Hosts information is correct - PASS
- 8.6 Host attachment points to the network - FAIL
- PASS
- 8.7 Clusters view is consistent across all ONOS nodes - PASS
- 8.8 There is only one SCC - PASS
- 8.9 Device information is correct - PASS
- 8.10 Port information is correct - PASS
- 8.11 Links are correct - PASS
- 8.12 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sendind traffic across Intents -
...
PASS
Ping across added host intents to check functionality and check the state of the intent
- 4.1 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- PASS
- 4.2 Check Intent state - PASS
- 4.3 Check leadership of topics - PASS
- 4. 4 Wait a minute then ping again - FAIL
- .4 Wait a minute then ping again - PASS
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 -
...
PASS
Compare topology objects between Mininet and ONOS
- 8.1 Create TestONTopology object - PASS
- 8.2 Comparing ONOS topology to MN - No Result
- 8.3 Collecting topology information from ONOS - PASS
- 8.4 Hosts view is consistent across all ONOS nodes - PASS
- 8.5 Hosts information is correct - PASS
- 8.6 Host attachment points to the network - FAIL
- ONOS did not correctly attach hosts to the network
- PASS
- 8.7 Clusters view is consistent across all ONOS nodes - PASS
- 8.8 There is only one SCC - PASS
- 8.9 Device information is correct - PASS
- 8.10 Port information is correct - PASS
- 8.11 Links are correct - PASS
- 8.12 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sendind traffic across Intents -
...
PASS
Ping across added host intents to check functionality and check the state of the intent
- 4.1 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- PASS
- 4.2 Check Intent state - PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - FAIL
- PASS
Case 13: Test Cleanup - PASS
...