**************************************
Jenkins test result for 02:49 on Dec 11, 2014.Test HATestSanity
************************************
Result summary for Testcase1
ONOS HA Sanity test - initialization
Removing raft logs
Uninstalling ONOS
commit 550923b0d1094a74b2905df41ea7a8a2f24ef23f (HEAD, review/yuta_higuchi/ONOS-436)
Author: Jon Hall [JHall@onlab.us]
AuthorDate: Wed Dec 10 18:55:57 2014 -0500
Commit: Jon Hall [JHall@onlab.us]
CommitDate: Wed Dec 10 18:55:57 2014 -0500
Tracking down NPE
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.3542289734 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 Testcase14
Result: Pass
Result summary for Testcase6
Wait 60 seconds instead of inducing a failure
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.5441050529 seconds, 1 tries
ONOS topology view matches Mininet topology
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 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.7089178562 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.5094571114 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.5668311119 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.4550449848 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 550923b0d1094a74b2905df41ea7a8a2f24ef23f (HEAD, review/yuta_higuchi/ONOS-436)
Author: Jon Hall [JHall@onlab.us]
AuthorDate: Wed Dec 10 18:55:57 2014 -0500
Commit: Jon Hall [JHall@onlab.us]
CommitDate: Wed Dec 10 18:55:57 2014 -0500
Tracking down NPE
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.1279830933 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 Testcase8
Compare ONOS Topology view to Mininet topology
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 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 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.8633060455 seconds, 3 tries
Topology Check Test NOT successful
Result: Failed
Result summary for Testcase7
Switch roles are consistent across all ONOS nodes
Mastership of some switches changed
Intents are consistent across all ONOS nodes
The Intents changed during failure
Changes were found in the flow tables
Loss of dataplane connectivity detected
Constant state tests failed
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
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 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 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.5105791092 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
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 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 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.4572589397 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: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
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 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 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.0545990467 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: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
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 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 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.5084679127 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 550923b0d1094a74b2905df41ea7a8a2f24ef23f (HEAD, review/yuta_higuchi/ONOS-436)
Author: Jon Hall [JHall@onlab.us]
AuthorDate: Wed Dec 10 18:55:57 2014 -0500
Commit: Jon Hall [JHall@onlab.us]
CommitDate: Wed Dec 10 18:55:57 2014 -0500
Tracking down NPE
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.7802908421 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 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
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): 39.6543211937 seconds, 2 tries
ONOS topology view matches Mininet topology
Result: Pass
Result summary for Testcase3
Adding host intents
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 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.5221641064 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.600135088 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.5224120617 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.3751480579 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 SingleInstanceHATestRestart
************************************
Result summary for Testcase1
ONOS Single node cluster restart HA test - initialization
Removing raft logs
Uninstalling ONOS
commit 550923b0d1094a74b2905df41ea7a8a2f24ef23f (HEAD, review/yuta_higuchi/ONOS-436)
Author: Jon Hall [JHall@onlab.us]
AuthorDate: Wed Dec 10 18:55:57 2014 -0500
Commit: Jon Hall [JHall@onlab.us]
CommitDate: Wed Dec 10 18:55:57 2014 -0500
Tracking down NPE
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