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.
**************************************
Jenkins test result for 19:48 on Dec 03, 2014.Test HATestSanity
************************************
Result summary for Testcase1
ONOS HA Sanity test - initialization
Removing raft logs
Uninstalling ONOS
commit eb8e3ea61af693118bcee7d8984756a0d8bffa4f (HEAD, origin/master, origin/HEAD, master)
Author: Brian O'Connor [bocon@onlab.us]
AuthorDate: Wed Dec 3 17:53:33 2014 -0800
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Thu Dec 4 02:54:43 2014 +0000
adding staging repository before release
Result: Pass
Result summary for Testcase2
Assigning switches to controllers
Switch mastership assigned correctly
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Very crass estimate for topology discovery/convergence(note it takes about 13 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance): 13.8426480293 seconds, 1 tries
ONOS topology view matches Mininet topology
Result: Pass
Result summary for Testcase3
Adding host intents
Result: Pass
Result summary for Testcase4
Ping across added host intents
Intents have been installed correctly and verified by pings
Result: Pass
Result summary for Testcase5
Setting up and gathering data for current state
Switch roles are consistent across all ONOS nodes
Intents are consistent across all ONOS nodes
Flow count is consistent across all ONOS nodes
Result: Pass
Result summary for Testcase6
Wait 60 seconds instead of inducing a failure
Result: Pass
Result summary for Testcase7
Switch roles are consistent across all ONOS nodes
Mastership of Switches was not changed
Intents are consistent across all ONOS nodes
Intents are consistent with before failure
No changes were found in the flow tables
No loss of dataplane connectivity
Constant State Tests Passed
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Very crass estimate for topology discovery/convergence(note it takes about 13 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance): 13.5194900036 seconds, 1 tries
ONOS topology view matches Mininet topology
Result: Pass
Result summary for Testcase4
Ping across added host intents
Intents have been installed correctly and verified by pings
Result: Pass
Result summary for Testcase9
Turn off a link to ensure that Link Discovery is working properly
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Very crass estimate for topology discovery/convergence(note it takes about 13 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance): 13.7368638515 seconds, 1 tries
ONOS topology view matches Mininet topology
Result: Pass
Result summary for Testcase4
Ping across added host intents
Intents have been installed correctly and verified by pings
Result: Pass
Result summary for Testcase10
Restore a link to ensure that Link Discovery is working properly
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Very crass estimate for topology discovery/convergence(note it takes about 13 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance): 13.6353709698 seconds, 1 tries
ONOS topology view matches Mininet topology
Result: Pass
Result summary for Testcase4
Ping across added host intents
Intents have been installed correctly and verified by pings
Result: Pass
Result summary for Testcase11
Killing a switch to ensure it is discovered correctly
Deleting s28
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Very crass estimate for topology discovery/convergence(note it takes about 13 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance): 13.5142278671 seconds, 1 tries
ONOS topology view matches Mininet topology
Result: Pass
Result summary for Testcase4
Ping across added host intents
Intents have been installed correctly and verified by pings
Result: Pass
Result summary for Testcase12
Adding a switch to ensure it is discovered correctly
Adding back s28
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Very crass estimate for topology discovery/convergence(note it takes about 13 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance): 13.662886858 seconds, 1 tries
ONOS topology view matches Mininet topology
Result: Pass
Result summary for Testcase4
Ping across added host intents
Intents have been installed correctly and verified by pings
Result: Pass
Result summary for Testcase13
Test Cleanup
Result: Pass
Test HATestMinorityRestart
************************************
Result summary for Testcase1
ONOS HA test: Restart minority of ONOS nodes - initialization
Removing raft logs
Uninstalling ONOS
commit eb8e3ea61af693118bcee7d8984756a0d8bffa4f (HEAD, origin/master, origin/HEAD, master)
Author: Brian O'Connor [bocon@onlab.us]
AuthorDate: Wed Dec 3 17:53:33 2014 -0800
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Thu Dec 4 02:54:43 2014 +0000
adding staging repository before release
Result: Pass
Result summary for Testcase2
Assigning switches to controllers
Switch mastership assigned correctly
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Very crass estimate for topology discovery/convergence(note it takes about 14 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance): 14.1264381409 seconds, 1 tries
ONOS topology view matches Mininet topology
Result: Pass
Result summary for Testcase3
Adding host intents
Result: Pass
Result summary for Testcase4
Ping across added host intents
Intents have been installed correctly and verified by pings
Result: Pass
Result summary for Testcase5
Setting up and gathering data for current state
Switch roles are consistent across all ONOS nodes
Intents are consistent across all ONOS nodes
Flow count is consistent across all ONOS nodes
Result: Pass
Result summary for Testcase6
Killing 3 ONOS nodes
Result: Pass
Result summary for Testcase7
Switch roles are consistent across all ONOS nodes
Mastership of some switches changed
Intents are consistent across all ONOS nodes
No changes were found in the flow tables
Loss of dataplane connectivity detected
Constant state tests failed
Result: Failed
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS1 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS2 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS3 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS4 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS5 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS6 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS7 links view is incorrect
clusters from ONOS4 is inconsistent with ONOS1
clusters from ONOS6 is inconsistent with ONOS1
clusters from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of clusters
ONOS shows 2 SCCs
paths from ONOS4 is inconsistent with ONOS1
paths from ONOS6 is inconsistent with ONOS1
paths from ONOS7 is inconsistent with ONOS1
ONOS nodes have different counts of paths
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS1 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS2 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS3 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS4 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS5 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS6 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS7 links view is incorrect
clusters from ONOS4 is inconsistent with ONOS1
clusters from ONOS6 is inconsistent with ONOS1
clusters from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of clusters
ONOS shows 2 SCCs
paths from ONOS4 is inconsistent with ONOS1
paths from ONOS6 is inconsistent with ONOS1
paths from ONOS7 is inconsistent with ONOS1
ONOS nodes have different counts of paths
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS1 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS2 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS3 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS4 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS5 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS6 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS7 links view is incorrect
clusters from ONOS4 is inconsistent with ONOS1
clusters from ONOS6 is inconsistent with ONOS1
clusters from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of clusters
ONOS shows 2 SCCs
paths from ONOS4 is inconsistent with ONOS1
paths from ONOS6 is inconsistent with ONOS1
paths from ONOS7 is inconsistent with ONOS1
ONOS nodes have different counts of paths
Very crass estimate for topology discovery/convergence(note it takes about 13 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance): 64.8920259476 seconds, 3 tries
Topology Check Test NOT successful
Result: Failed
Result summary for Testcase4
Ping across added host intents
Intents have not been installed correctly, pings failed.
Intents have not been installed correctly, pings failed.
Result: Failed
Result summary for Testcase9
Turn off a link to ensure that Link Discovery is working properly
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
The list of ports for switch s3(0000000000003000) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS1 ports view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS1 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS2 ports view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS2 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS3 ports view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS3 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS4 ports view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS4 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS5 ports view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS5 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS6 ports view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS6 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS7 ports view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS7 links view is incorrect
clusters from ONOS4 is inconsistent with ONOS1
clusters from ONOS6 is inconsistent with ONOS1
clusters from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of clusters
ONOS shows 2 SCCs
paths from ONOS4 is inconsistent with ONOS1
paths from ONOS6 is inconsistent with ONOS1
paths from ONOS7 is inconsistent with ONOS1
ONOS nodes have different counts of paths
The list of ports for switch s3(0000000000003000) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS1 ports view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS1 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS2 ports view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS2 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS3 ports view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS3 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS4 ports view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS4 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS5 ports view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS5 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS6 ports view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS6 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS7 ports view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS7 links view is incorrect
clusters from ONOS4 is inconsistent with ONOS1
clusters from ONOS6 is inconsistent with ONOS1
clusters from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of clusters
ONOS shows 2 SCCs
paths from ONOS4 is inconsistent with ONOS1
paths from ONOS6 is inconsistent with ONOS1
paths from ONOS7 is inconsistent with ONOS1
ONOS nodes have different counts of paths
The list of ports for switch s3(0000000000003000) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS1 ports view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS1 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS2 ports view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS2 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS3 ports view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS3 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS4 ports view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS4 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS5 ports view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS5 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS6 ports view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS6 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS7 ports view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS7 links view is incorrect
clusters from ONOS4 is inconsistent with ONOS1
clusters from ONOS6 is inconsistent with ONOS1
clusters from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of clusters
ONOS shows 2 SCCs
paths from ONOS4 is inconsistent with ONOS1
paths from ONOS6 is inconsistent with ONOS1
paths from ONOS7 is inconsistent with ONOS1
ONOS nodes have different counts of paths
Very crass estimate for topology discovery/convergence(note it takes about 13 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance): 65.0317177773 seconds, 3 tries
Topology Check Test NOT successful
Result: Failed
Result summary for Testcase4
Ping across added host intents
Intents have not been installed correctly, pings failed.
Intents have not been installed correctly, pings failed.
Result: Failed
Result summary for Testcase10
Restore a link to ensure that Link Discovery is working properly
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS1 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS2 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS3 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS4 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS5 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS6 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS7 links view is incorrect
clusters from ONOS4 is inconsistent with ONOS1
clusters from ONOS6 is inconsistent with ONOS1
clusters from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of clusters
ONOS shows 2 SCCs
paths from ONOS4 is inconsistent with ONOS1
paths from ONOS6 is inconsistent with ONOS1
paths from ONOS7 is inconsistent with ONOS1
ONOS nodes have different counts of paths
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS1 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS2 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS3 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS4 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS5 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS6 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS7 links view is incorrect
clusters from ONOS4 is inconsistent with ONOS1
clusters from ONOS6 is inconsistent with ONOS1
clusters from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of clusters
ONOS shows 2 SCCs
paths from ONOS4 is inconsistent with ONOS1
paths from ONOS6 is inconsistent with ONOS1
paths from ONOS7 is inconsistent with ONOS1
ONOS nodes have different counts of paths
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS1 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS2 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS3 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS4 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS5 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS6 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 57 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS7 links view is incorrect
clusters from ONOS4 is inconsistent with ONOS1
clusters from ONOS6 is inconsistent with ONOS1
clusters from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of clusters
ONOS shows 2 SCCs
paths from ONOS4 is inconsistent with ONOS1
paths from ONOS6 is inconsistent with ONOS1
paths from ONOS7 is inconsistent with ONOS1
ONOS nodes have different counts of paths
Very crass estimate for topology discovery/convergence(note it takes about 13 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance): 64.5795631409 seconds, 3 tries
Topology Check Test NOT successful
Result: Failed
Result summary for Testcase4
Ping across added host intents
Intents have not been installed correctly, pings failed.
Intents have not been installed correctly, pings failed.
Result: Failed
Result summary for Testcase11
Killing a switch to ensure it is discovered correctly
Deleting s28
Result: Failed
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
The list of ports for switch s3(0000000000003000) does not match:
ONOS1 ports view is incorrect
Mininet has 27 bidirectional links and ONOS has 56 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS1 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS2 ports view is incorrect
Mininet has 27 bidirectional links and ONOS has 56 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS2 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS3 ports view is incorrect
Mininet has 27 bidirectional links and ONOS has 56 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS3 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS4 ports view is incorrect
Mininet has 27 bidirectional links and ONOS has 56 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS4 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS5 ports view is incorrect
Mininet has 27 bidirectional links and ONOS has 56 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS5 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS6 ports view is incorrect
Mininet has 27 bidirectional links and ONOS has 56 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS6 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS7 ports view is incorrect
Mininet has 27 bidirectional links and ONOS has 56 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS7 links view is incorrect
clusters from ONOS4 is inconsistent with ONOS1
clusters from ONOS6 is inconsistent with ONOS1
clusters from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of clusters
ONOS shows 2 SCCs
paths from ONOS4 is inconsistent with ONOS1
paths from ONOS6 is inconsistent with ONOS1
paths from ONOS7 is inconsistent with ONOS1
ONOS nodes have different counts of paths
The list of ports for switch s3(0000000000003000) does not match:
ONOS1 ports view is incorrect
Mininet has 27 bidirectional links and ONOS has 56 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS1 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS2 ports view is incorrect
Mininet has 27 bidirectional links and ONOS has 56 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS2 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS3 ports view is incorrect
Mininet has 27 bidirectional links and ONOS has 56 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS3 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS4 ports view is incorrect
Mininet has 27 bidirectional links and ONOS has 56 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS4 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS5 ports view is incorrect
Mininet has 27 bidirectional links and ONOS has 56 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS5 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS6 ports view is incorrect
Mininet has 27 bidirectional links and ONOS has 56 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS6 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS7 ports view is incorrect
Mininet has 27 bidirectional links and ONOS has 56 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS7 links view is incorrect
clusters from ONOS4 is inconsistent with ONOS1
clusters from ONOS6 is inconsistent with ONOS1
clusters from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of clusters
ONOS shows 2 SCCs
paths from ONOS4 is inconsistent with ONOS1
paths from ONOS6 is inconsistent with ONOS1
paths from ONOS7 is inconsistent with ONOS1
ONOS nodes have different counts of paths
The list of ports for switch s3(0000000000003000) does not match:
ONOS1 ports view is incorrect
Mininet has 27 bidirectional links and ONOS has 56 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS1 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS2 ports view is incorrect
Mininet has 27 bidirectional links and ONOS has 56 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS2 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS3 ports view is incorrect
Mininet has 27 bidirectional links and ONOS has 56 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS3 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS4 ports view is incorrect
Mininet has 27 bidirectional links and ONOS has 56 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS4 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS5 ports view is incorrect
Mininet has 27 bidirectional links and ONOS has 56 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS5 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS6 ports view is incorrect
Mininet has 27 bidirectional links and ONOS has 56 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS6 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS7 ports view is incorrect
Mininet has 27 bidirectional links and ONOS has 56 unidirectional links
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS7 links view is incorrect
clusters from ONOS4 is inconsistent with ONOS1
clusters from ONOS6 is inconsistent with ONOS1
clusters from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of clusters
ONOS shows 2 SCCs
paths from ONOS4 is inconsistent with ONOS1
paths from ONOS6 is inconsistent with ONOS1
paths from ONOS7 is inconsistent with ONOS1
ONOS nodes have different counts of paths
Very crass estimate for topology discovery/convergence(note it takes about 13 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance): 64.4739060402 seconds, 3 tries
Topology Check Test NOT successful
Result: Failed
Result summary for Testcase4
Ping across added host intents
Intents have not been installed correctly, pings failed.
Intents have not been installed correctly, pings failed.
Result: Failed
Result summary for Testcase12
Adding a switch to ensure it is discovered correctly
Adding back s28
Result: Failed
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
The list of ports for switch s3(0000000000003000) does not match:
ONOS1 ports view is incorrect
ONOS does not have the link 0000000000003000/5 -> 0000000000002800/1
ONOS does not have the link 0000000000002800/1 -> 0000000000003000/5
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS1 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS2 ports view is incorrect
ONOS does not have the link 0000000000003000/5 -> 0000000000002800/1
ONOS does not have the link 0000000000002800/1 -> 0000000000003000/5
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS2 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS3 ports view is incorrect
ONOS does not have the link 0000000000003000/5 -> 0000000000002800/1
ONOS does not have the link 0000000000002800/1 -> 0000000000003000/5
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS3 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS4 ports view is incorrect
ONOS does not have the link 0000000000003000/5 -> 0000000000002800/1
ONOS does not have the link 0000000000002800/1 -> 0000000000003000/5
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS4 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS5 ports view is incorrect
ONOS does not have the link 0000000000003000/5 -> 0000000000002800/1
ONOS does not have the link 0000000000002800/1 -> 0000000000003000/5
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS5 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS6 ports view is incorrect
ONOS does not have the link 0000000000003000/5 -> 0000000000002800/1
ONOS does not have the link 0000000000002800/1 -> 0000000000003000/5
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS6 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS7 ports view is incorrect
ONOS does not have the link 0000000000003000/5 -> 0000000000002800/1
ONOS does not have the link 0000000000002800/1 -> 0000000000003000/5
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS7 links view is incorrect
clusters from ONOS4 is inconsistent with ONOS1
clusters from ONOS6 is inconsistent with ONOS1
clusters from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of clusters
ONOS shows 2 SCCs
paths from ONOS4 is inconsistent with ONOS1
paths from ONOS6 is inconsistent with ONOS1
paths from ONOS7 is inconsistent with ONOS1
ONOS nodes have different counts of paths
The list of ports for switch s3(0000000000003000) does not match:
ONOS1 ports view is incorrect
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS does not have the link 0000000000003000/5 -> 0000000000002800/1
ONOS does not have the link 0000000000002800/1 -> 0000000000003000/5
ONOS1 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS2 ports view is incorrect
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS does not have the link 0000000000003000/5 -> 0000000000002800/1
ONOS does not have the link 0000000000002800/1 -> 0000000000003000/5
ONOS2 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS3 ports view is incorrect
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS does not have the link 0000000000003000/5 -> 0000000000002800/1
ONOS does not have the link 0000000000002800/1 -> 0000000000003000/5
ONOS3 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS4 ports view is incorrect
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS does not have the link 0000000000003000/5 -> 0000000000002800/1
ONOS does not have the link 0000000000002800/1 -> 0000000000003000/5
ONOS4 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS5 ports view is incorrect
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS does not have the link 0000000000003000/5 -> 0000000000002800/1
ONOS does not have the link 0000000000002800/1 -> 0000000000003000/5
ONOS5 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS6 ports view is incorrect
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS does not have the link 0000000000003000/5 -> 0000000000002800/1
ONOS does not have the link 0000000000002800/1 -> 0000000000003000/5
ONOS6 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS7 ports view is incorrect
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS does not have the link 0000000000003000/5 -> 0000000000002800/1
ONOS does not have the link 0000000000002800/1 -> 0000000000003000/5
ONOS7 links view is incorrect
clusters from ONOS4 is inconsistent with ONOS1
clusters from ONOS6 is inconsistent with ONOS1
clusters from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of clusters
ONOS shows 2 SCCs
paths from ONOS4 is inconsistent with ONOS1
paths from ONOS6 is inconsistent with ONOS1
paths from ONOS7 is inconsistent with ONOS1
ONOS nodes have different counts of paths
The list of ports for switch s3(0000000000003000) does not match:
ONOS1 ports view is incorrect
ONOS does not have the link 0000000000003000/5 -> 0000000000002800/1
ONOS does not have the link 0000000000002800/1 -> 0000000000003000/5
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS1 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS2 ports view is incorrect
ONOS does not have the link 0000000000003000/5 -> 0000000000002800/1
ONOS does not have the link 0000000000002800/1 -> 0000000000003000/5
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS2 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS3 ports view is incorrect
ONOS does not have the link 0000000000003000/5 -> 0000000000002800/1
ONOS does not have the link 0000000000002800/1 -> 0000000000003000/5
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS3 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS4 ports view is incorrect
ONOS does not have the link 0000000000003000/5 -> 0000000000002800/1
ONOS does not have the link 0000000000002800/1 -> 0000000000003000/5
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS4 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS5 ports view is incorrect
ONOS does not have the link 0000000000003000/5 -> 0000000000002800/1
ONOS does not have the link 0000000000002800/1 -> 0000000000003000/5
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS5 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS6 ports view is incorrect
ONOS does not have the link 0000000000003000/5 -> 0000000000002800/1
ONOS does not have the link 0000000000002800/1 -> 0000000000003000/5
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS6 links view is incorrect
The list of ports for switch s3(0000000000003000) does not match:
ONOS7 ports view is incorrect
ONOS does not have the link 0000000000003000/5 -> 0000000000002800/1
ONOS does not have the link 0000000000002800/1 -> 0000000000003000/5
ONOS does not have the link 0000000000003000/4 -> 0000000000003004/2
ONOS7 links view is incorrect
clusters from ONOS4 is inconsistent with ONOS1
clusters from ONOS6 is inconsistent with ONOS1
clusters from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of clusters
ONOS shows 2 SCCs
paths from ONOS4 is inconsistent with ONOS1
paths from ONOS6 is inconsistent with ONOS1
paths from ONOS7 is inconsistent with ONOS1
ONOS nodes have different counts of paths
Very crass estimate for topology discovery/convergence(note it takes about 13 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance): 65.0261039734 seconds, 3 tries
Topology Check Test NOT successful
Result: Failed
Result summary for Testcase4
Ping across added host intents
Intents have not been installed correctly, pings failed.
Intents have not been installed correctly, pings failed.
Result: Failed
Result summary for Testcase13
Test Cleanup
Result: Pass
Test HATestClusterRestart
************************************
Result summary for Testcase1
ONOS HA test: Restart all ONOS nodes - initialization
Removing raft logs
Uninstalling ONOS
commit eb8e3ea61af693118bcee7d8984756a0d8bffa4f (HEAD, origin/master, origin/HEAD, master)
Author: Brian O'Connor [bocon@onlab.us]
AuthorDate: Wed Dec 3 17:53:33 2014 -0800
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Thu Dec 4 02:54:43 2014 +0000
adding staging repository before release
Result: Pass
Result summary for Testcase2
Assigning switches to controllers
Switch mastership assigned correctly
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Very crass estimate for topology discovery/convergence(note it takes about 13 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance): 13.6384510994 seconds, 1 tries
ONOS topology view matches Mininet topology
Result: Pass
Result summary for Testcase3
Adding host intents
Result: Pass
Result summary for Testcase4
Ping across added host intents
Intents have been installed correctly and verified by pings
Result: Pass
Result summary for Testcase5
Setting up and gathering data for current state
Switch roles are consistent across all ONOS nodes
Intents are consistent across all ONOS nodes
Flow count is consistent across all ONOS nodes
Result: Pass
Result summary for Testcase6
Restart entire ONOS cluster
Result: Pass
Result summary for Testcase7
Switch roles are consistent across all ONOS nodes
Mastership of some switches changed
Intents are consistent across all ONOS nodes
No changes were found in the flow tables
Loss of dataplane connectivity detected
Constant state tests failed
Result: Failed
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
hosts from ONOS2 is inconsistent with ONOS1
hosts from ONOS3 is inconsistent with ONOS1
hosts from ONOS4 is inconsistent with ONOS1
hosts from ONOS5 is inconsistent with ONOS1
hosts from ONOS6 is inconsistent with ONOS1
hosts from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of hosts
hosts from ONOS2 is inconsistent with ONOS1
hosts from ONOS3 is inconsistent with ONOS1
hosts from ONOS4 is inconsistent with ONOS1
hosts from ONOS5 is inconsistent with ONOS1
hosts from ONOS6 is inconsistent with ONOS1
hosts from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of hosts
hosts from ONOS2 is inconsistent with ONOS1
hosts from ONOS3 is inconsistent with ONOS1
hosts from ONOS4 is inconsistent with ONOS1
hosts from ONOS5 is inconsistent with ONOS1
hosts from ONOS6 is inconsistent with ONOS1
hosts from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of hosts
Very crass estimate for topology discovery/convergence(note it takes about 13 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance): 64.4338650703 seconds, 3 tries
Topology Check Test NOT successful
Result: Failed
Result summary for Testcase4
Ping across added host intents
Intents have been installed correctly and verified by pings
Result: Pass
Result summary for Testcase9
Turn off a link to ensure that Link Discovery is working properly
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
hosts from ONOS2 is inconsistent with ONOS1
hosts from ONOS3 is inconsistent with ONOS1
hosts from ONOS4 is inconsistent with ONOS1
hosts from ONOS5 is inconsistent with ONOS1
hosts from ONOS6 is inconsistent with ONOS1
hosts from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of hosts
hosts from ONOS2 is inconsistent with ONOS1
hosts from ONOS3 is inconsistent with ONOS1
hosts from ONOS4 is inconsistent with ONOS1
hosts from ONOS5 is inconsistent with ONOS1
hosts from ONOS6 is inconsistent with ONOS1
hosts from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of hosts
hosts from ONOS2 is inconsistent with ONOS1
hosts from ONOS3 is inconsistent with ONOS1
hosts from ONOS4 is inconsistent with ONOS1
hosts from ONOS5 is inconsistent with ONOS1
hosts from ONOS6 is inconsistent with ONOS1
hosts from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of hosts
Very crass estimate for topology discovery/convergence(note it takes about 13 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance): 64.3012619019 seconds, 3 tries
Topology Check Test NOT successful
Result: Failed
Result summary for Testcase4
Ping across added host intents
Intents have been installed correctly and verified by pings
Result: Pass
Result summary for Testcase10
Restore a link to ensure that Link Discovery is working properly
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
hosts from ONOS2 is inconsistent with ONOS1
hosts from ONOS3 is inconsistent with ONOS1
hosts from ONOS4 is inconsistent with ONOS1
hosts from ONOS5 is inconsistent with ONOS1
hosts from ONOS6 is inconsistent with ONOS1
hosts from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of hosts
hosts from ONOS2 is inconsistent with ONOS1
hosts from ONOS3 is inconsistent with ONOS1
hosts from ONOS4 is inconsistent with ONOS1
hosts from ONOS5 is inconsistent with ONOS1
hosts from ONOS6 is inconsistent with ONOS1
hosts from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of hosts
hosts from ONOS2 is inconsistent with ONOS1
hosts from ONOS3 is inconsistent with ONOS1
hosts from ONOS4 is inconsistent with ONOS1
hosts from ONOS5 is inconsistent with ONOS1
hosts from ONOS6 is inconsistent with ONOS1
hosts from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of hosts
Very crass estimate for topology discovery/convergence(note it takes about 13 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance): 64.4747331142 seconds, 3 tries
Topology Check Test NOT successful
Result: Failed
Result summary for Testcase4
Ping across added host intents
Intents have been installed correctly and verified by pings
Result: Pass
Result summary for Testcase11
Killing a switch to ensure it is discovered correctly
Deleting s28
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
hosts from ONOS2 is inconsistent with ONOS1
hosts from ONOS3 is inconsistent with ONOS1
hosts from ONOS4 is inconsistent with ONOS1
hosts from ONOS5 is inconsistent with ONOS1
hosts from ONOS6 is inconsistent with ONOS1
hosts from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of hosts
hosts from ONOS2 is inconsistent with ONOS1
hosts from ONOS3 is inconsistent with ONOS1
hosts from ONOS4 is inconsistent with ONOS1
hosts from ONOS5 is inconsistent with ONOS1
hosts from ONOS6 is inconsistent with ONOS1
hosts from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of hosts
hosts from ONOS2 is inconsistent with ONOS1
hosts from ONOS3 is inconsistent with ONOS1
hosts from ONOS4 is inconsistent with ONOS1
hosts from ONOS5 is inconsistent with ONOS1
hosts from ONOS6 is inconsistent with ONOS1
hosts from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of hosts
Very crass estimate for topology discovery/convergence(note it takes about 13 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance): 63.7735669613 seconds, 3 tries
Topology Check Test NOT successful
Result: Failed
Result summary for Testcase4
Ping across added host intents
Intents have been installed correctly and verified by pings
Result: Pass
Result summary for Testcase12
Adding a switch to ensure it is discovered correctly
Adding back s28
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
hosts from ONOS2 is inconsistent with ONOS1
hosts from ONOS3 is inconsistent with ONOS1
hosts from ONOS4 is inconsistent with ONOS1
hosts from ONOS5 is inconsistent with ONOS1
hosts from ONOS6 is inconsistent with ONOS1
hosts from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of hosts
hosts from ONOS2 is inconsistent with ONOS1
hosts from ONOS3 is inconsistent with ONOS1
hosts from ONOS4 is inconsistent with ONOS1
hosts from ONOS5 is inconsistent with ONOS1
hosts from ONOS6 is inconsistent with ONOS1
hosts from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of hosts
hosts from ONOS2 is inconsistent with ONOS1
hosts from ONOS3 is inconsistent with ONOS1
hosts from ONOS4 is inconsistent with ONOS1
hosts from ONOS5 is inconsistent with ONOS1
hosts from ONOS6 is inconsistent with ONOS1
hosts from ONOS7 is inconsistent with ONOS1
ONOS nodes have different views of hosts
Very crass estimate for topology discovery/convergence(note it takes about 13 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance): 64.3621809483 seconds, 3 tries
Topology Check Test NOT successful
Result: Failed
Result summary for Testcase4
Ping across added host intents
Intents have been installed correctly and verified by pings
Result: Pass
Result summary for Testcase13
Test Cleanup
Result: Pass
Test SingleInstanceHATestRestart
************************************
Result summary for Testcase1
ONOS Single node cluster restart HA test - initialization
Removing raft logs
Uninstalling ONOS
commit eb8e3ea61af693118bcee7d8984756a0d8bffa4f (HEAD, origin/master, origin/HEAD, master)
Author: Brian O'Connor [bocon@onlab.us]
AuthorDate: Wed Dec 3 17:53:33 2014 -0800
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Thu Dec 4 02:54:43 2014 +0000
adding staging repository before release
Result: Pass
Result summary for Testcase2
Assigning switches to controllers
Switch mastership assigned correctly
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Very crass estimate for topology discovery/convergence(note it takes about 1 seconds to read the topology from each ONOS instance): 1.10680103302 seconds, 1 tries
ONOS topology view matches Mininet topology
Result: Pass
Result summary for Testcase3
Adding host intents
Result: Pass
Result summary for Testcase4
Ping across added host intents
Intents have been installed correctly and verified by pings
Result: Pass
Result summary for Testcase5
Setting up and gathering data for current state
Result: Pass
Result summary for Testcase6
Restart ONOS node
Result: Pass
Result summary for Testcase7
Switch roles are consistent across all ONOS nodes
Mastership of Switches was not changed
Intents are consistent across all ONOS nodes
No changes were found in the flow tables
Loss of dataplane connectivity detected
Constant State Tests Passed
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Very crass estimate for topology discovery/convergence(note it takes about 1 seconds to read the topology from each ONOS instance): 0.980257034302 seconds, 1 tries
ONOS topology view matches Mininet topology
Result: Pass
Result summary for Testcase4
Ping across added host intents
Intents have been installed correctly and verified by pings
Result: Pass
Result summary for Testcase9
Turn off a link to ensure that Link Discovery is working properly
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Very crass estimate for topology discovery/convergence(note it takes about 1 seconds to read the topology from each ONOS instance): 0.944633960724 seconds, 1 tries
ONOS topology view matches Mininet topology
Result: Pass
Result summary for Testcase4
Ping across added host intents
Intents have been installed correctly and verified by pings
Result: Pass
Result summary for Testcase10
Restore a link to ensure that Link Discovery is working properly
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Very crass estimate for topology discovery/convergence(note it takes about 1 seconds to read the topology from each ONOS instance): 0.946712017059 seconds, 1 tries
ONOS topology view matches Mininet topology
Result: Pass
Result summary for Testcase4
Ping across added host intents
Intents have been installed correctly and verified by pings
Result: Pass
Result summary for Testcase11
Killing a switch to ensure it is discovered correctly
Deleting s28
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Very crass estimate for topology discovery/convergence(note it takes about 1 seconds to read the topology from each ONOS instance): 0.905240058899 seconds, 1 tries
ONOS topology view matches Mininet topology
Result: Pass
Result summary for Testcase4
Ping across added host intents
Intents have been installed correctly and verified by pings
Result: Pass
Result summary for Testcase12
Adding a switch to ensure it is discovered correctly
Adding back s28
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Very crass estimate for topology discovery/convergence(note it takes about 1 seconds to read the topology from each ONOS instance): 0.933022022247 seconds, 1 tries
ONOS topology view matches Mininet topology
Result: Pass
Result summary for Testcase4
Ping across added host intents
Intents have been installed correctly and verified by pings
Result: Pass
Result summary for Testcase13
Test Cleanup
Result: Pass