**************************************
Jenkins test result for 19:02 on Dec 03, 2014.Test HATestSanity
************************************
Result summary for Testcase1
ONOS HA Sanity test - initialization
Removing raft logs
Uninstalling ONOS
commit 369c64380201c450881ffb666c40526c48cb4d5d (HEAD, origin/master, origin/HEAD, master)
Author: Pavlin Radoslavov [pavlin@onlab.us]
AuthorDate: Wed Dec 3 16:25:14 2014 -0800
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Thu Dec 4 02:06:53 2014 +0000
Use two thread pools for handling the OpenFlow STATS and BARRIER messages.
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.1615219116 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.7236478329 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.6951830387 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.6894640923 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.6178030968 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.5424029827 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 369c64380201c450881ffb666c40526c48cb4d5d (HEAD, origin/master, origin/HEAD, master)
Author: Pavlin Radoslavov [pavlin@onlab.us]
AuthorDate: Wed Dec 3 16:25:14 2014 -0800
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Thu Dec 4 02:06:53 2014 +0000
Use two thread pools for handling the OpenFlow STATS and BARRIER messages.
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.737183094 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.946876049 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 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 19 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance): 19.4245178699 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.4693520069 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 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
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.81072402 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.6714758873 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 369c64380201c450881ffb666c40526c48cb4d5d (HEAD, origin/master, origin/HEAD, master)
Author: Pavlin Radoslavov [pavlin@onlab.us]
AuthorDate: Wed Dec 3 16:25:14 2014 -0800
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Thu Dec 4 02:06:53 2014 +0000
Use two thread pools for handling the OpenFlow STATS and BARRIER messages.
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.1230700016 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): 65.0575289726 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.2791528702 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.3183898926 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.927738905 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): 65.2109000683 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 369c64380201c450881ffb666c40526c48cb4d5d (HEAD, origin/master, origin/HEAD, master)
Author: Pavlin Radoslavov [pavlin@onlab.us]
AuthorDate: Wed Dec 3 16:25:14 2014 -0800
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Thu Dec 4 02:06:53 2014 +0000
Use two thread pools for handling the OpenFlow STATS and BARRIER messages.
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.04458904266 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.932883024216 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.927493095398 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.915009021759 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.932729005814 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.920262098312 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