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 00:26 on Dec 04, 2014.Test HATestSanity
************************************
Result summary for Testcase1
ONOS HA Sanity test - initialization
Removing raft logs
Uninstalling ONOS
commit 9796cc623d5aa3e0a9537f0f125d1abf37e386f4 (HEAD, origin/master, origin/HEAD, master)
Author: Yuta HIGUCHI [y-higuchi@ak.jp.nec.com]
AuthorDate: Wed Dec 3 16:24:13 2014 -0800
Commit: Yuta Higuchi [y-higuchi@onlab.us]
CommitDate: Thu Dec 4 07:10:55 2014 +0000
HazelcastIntentStore: workaround to provide Event subject on WITHDRAWN
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.016753912 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.7793209553 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.6316900253 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.8270409107 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.9167840481 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.9083418846 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 9796cc623d5aa3e0a9537f0f125d1abf37e386f4 (HEAD, origin/master, origin/HEAD, master)
Author: Yuta HIGUCHI [y-higuchi@ak.jp.nec.com]
AuthorDate: Wed Dec 3 16:24:13 2014 -0800
Commit: Yuta Higuchi [y-higuchi@onlab.us]
CommitDate: Thu Dec 4 07:10:55 2014 +0000
HazelcastIntentStore: workaround to provide Event subject on WITHDRAWN
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.9523169994 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
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.4982168674 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.6910719872 seconds, 1 tries
ONOS topology view matches Mininet topology
Result: Pass
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
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.6650950909 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.5192110538 seconds, 1 tries
ONOS topology view matches Mininet topology
Result: Pass
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
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.6377351284 seconds, 1 tries
ONOS topology view matches Mininet topology
Result: Pass
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 9796cc623d5aa3e0a9537f0f125d1abf37e386f4 (HEAD, origin/master, origin/HEAD, master)
Author: Yuta HIGUCHI [y-higuchi@ak.jp.nec.com]
AuthorDate: Wed Dec 3 16:24:13 2014 -0800
Commit: Yuta Higuchi [y-higuchi@onlab.us]
CommitDate: Thu Dec 4 07:10:55 2014 +0000
HazelcastIntentStore: workaround to provide Event subject on WITHDRAWN
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.8019249439 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.4456689358 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.313680172 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): 63.9419569969 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): 64.5085449219 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.7634160519 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 9796cc623d5aa3e0a9537f0f125d1abf37e386f4 (HEAD, origin/master, origin/HEAD, master)
Author: Yuta HIGUCHI [y-higuchi@ak.jp.nec.com]
AuthorDate: Wed Dec 3 16:24:13 2014 -0800
Commit: Yuta Higuchi [y-higuchi@onlab.us]
CommitDate: Thu Dec 4 07:10:55 2014 +0000
HazelcastIntentStore: workaround to provide Event subject on WITHDRAWN
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.03535699844 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
Mininet has 29 bidirectional links and ONOS has 59 unidirectional links
ONOS1 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 59 unidirectional links
ONOS1 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 59 unidirectional links
ONOS1 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 59 unidirectional links
ONOS1 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 59 unidirectional links
ONOS1 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 59 unidirectional links
ONOS1 links view is incorrect
Very crass estimate for topology discovery/convergence(note it takes about 1 seconds to read the topology from each ONOS instance): 64.7579638958 seconds, 6 tries
Giving up on topology convergence
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
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS1 links view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS1 links view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS1 links view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS1 links view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS1 links view is incorrect
Mininet has 28 bidirectional links and ONOS has 57 unidirectional links
ONOS1 links view is incorrect
Very crass estimate for topology discovery/convergence(note it takes about 1 seconds to read the topology from each ONOS instance): 64.458078146 seconds, 6 tries
Giving up on topology convergence
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
Mininet has 29 bidirectional links and ONOS has 59 unidirectional links
ONOS1 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 59 unidirectional links
ONOS1 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 59 unidirectional links
ONOS1 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 59 unidirectional links
ONOS1 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 59 unidirectional links
ONOS1 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 59 unidirectional links
ONOS1 links view is incorrect
Very crass estimate for topology discovery/convergence(note it takes about 1 seconds to read the topology from each ONOS instance): 64.8155510426 seconds, 6 tries
Giving up on topology convergence
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
Mininet has 27 bidirectional links and ONOS has 55 unidirectional links
ONOS1 links view is incorrect
Mininet has 27 bidirectional links and ONOS has 55 unidirectional links
ONOS1 links view is incorrect
Mininet has 27 bidirectional links and ONOS has 55 unidirectional links
ONOS1 links view is incorrect
Mininet has 27 bidirectional links and ONOS has 55 unidirectional links
ONOS1 links view is incorrect
Mininet has 27 bidirectional links and ONOS has 55 unidirectional links
ONOS1 links view is incorrect
Mininet has 27 bidirectional links and ONOS has 55 unidirectional links
ONOS1 links view is incorrect
Very crass estimate for topology discovery/convergence(note it takes about 1 seconds to read the topology from each ONOS instance): 63.3181970119 seconds, 6 tries
Giving up on topology convergence
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
Mininet has 29 bidirectional links and ONOS has 59 unidirectional links
ONOS1 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 59 unidirectional links
ONOS1 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 59 unidirectional links
ONOS1 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 59 unidirectional links
ONOS1 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 59 unidirectional links
ONOS1 links view is incorrect
Mininet has 29 bidirectional links and ONOS has 59 unidirectional links
ONOS1 links view is incorrect
Very crass estimate for topology discovery/convergence(note it takes about 1 seconds to read the topology from each ONOS instance): 64.749215126 seconds, 6 tries
Giving up on topology convergence
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