**************************************
Jenkins test result for 20:36 on Jan 22, 2015.Test HATestSanity
************************************
Result summary for Testcase1
ONOS HA Sanity test - initialization
Removing raft logs
Uninstalling ONOS
commit 346609609ad1b522c8c50a0ed634c504b9408297 (HEAD, origin/master, origin/HEAD, master)
Author: Sho SHIMIZU [sshimizu@us.fujitsu.com]
AuthorDate: Thu Jan 22 17:58:44 2015 -0800
Commit: Sho SHIMIZU [sshimizu@us.fujitsu.com]
CommitDate: Thu Jan 22 17:58:44 2015 -0800
Fix typo in Javadoc comment
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 24 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance ): 24.731235981 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
Leadership election tests passed( consistent view of leader across listeners and a leader was elected )
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 24 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance ): 24.7542111874 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
Leadership election tests passed( consistent view of leader across listeners and a new leader was re-elected if applicable )
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 Testcase15
Check that Leadership Election is still functional
Leadership election tests passed( consistent view of leader across listeners and a new leader was elected when the old leader resigned )
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 25 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance ): 25.0013840199 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 25 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance ): 25.0363249779 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 s5
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Very crass estimate for topology discovery/convergence( note it takes about 24 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance ): 24.8804399967 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 s5
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Very crass estimate for topology discovery/convergence( note it takes about 24 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance ): 24.9342038631 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 346609609ad1b522c8c50a0ed634c504b9408297 (HEAD, origin/master, origin/HEAD, master)
Author: Sho SHIMIZU [sshimizu@us.fujitsu.com]
AuthorDate: Thu Jan 22 17:58:44 2015 -0800
Commit: Sho SHIMIZU [sshimizu@us.fujitsu.com]
CommitDate: Thu Jan 22 17:58:44 2015 -0800
Fix typo in Javadoc comment
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 24 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance ): 24.5783660412 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
Leadership election tests passed( consistent view of leader across listeners and a leader was elected )
Result: Pass
Result summary for Testcase6
Killing 3 ONOS nodes
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Very crass estimate for topology discovery/convergence( note it takes about 24 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance ): 24.8469779491 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 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
Leadership election tests passed( consistent view of leader across listeners and a new leader was re-elected if applicable )
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 Testcase15
Check that Leadership Election is still functional
Leadership election tests passed( consistent view of leader across listeners and a new leader was elected when the old leader resigned )
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 24 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance ): 24.8743009567 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 24 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance ): 24.5571398735 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 s5
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Very crass estimate for topology discovery/convergence( note it takes about 24 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance ): 24.5677499771 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 s5
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Very crass estimate for topology discovery/convergence( note it takes about 25 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance ): 25.1160860062 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 346609609ad1b522c8c50a0ed634c504b9408297 (HEAD, origin/master, origin/HEAD, master)
Author: Sho SHIMIZU [sshimizu@us.fujitsu.com]
AuthorDate: Thu Jan 22 17:58:44 2015 -0800
Commit: Sho SHIMIZU [sshimizu@us.fujitsu.com]
CommitDate: Thu Jan 22 17:58:44 2015 -0800
Fix typo in Javadoc comment
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 24 seconds for the test to make all the cli calls to fetch the topology from each ONOS instance ): 24.6825270653 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
Leadership election tests passed( consistent view of leader across listeners and a leader was elected )
Result: Pass
Result summary for Testcase6
Restart entire ONOS cluster
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Switches in MN but not in ONOS:
['0000000000003009', '0000000000003010', '0000000000003012', '0000000000006000', '0000000000006007', '0000000000006019', '0000000000006022']
Switches in ONOS but not in MN:
[]
ONOS1 Switches view is incorrect
The list of ports for switch s7(0000000000006007) does not match:
The list of ports for switch s6(0000000000006000) does not match:
The list of ports for switch s19(0000000000006019) does not match:
The list of ports for switch s13(0000000000003013) does not match:
The list of ports for switch s12(0000000000003012) does not match:
The list of ports for switch s10(0000000000003010) does not match:
The list of ports for switch s17(0000000000003017) does not match:
The list of ports for switch s9(0000000000003009) does not match:
The list of ports for switch s8(0000000000003008) does not match:
The list of ports for switch s22(0000000000006022) does not match:
ONOS1 ports view is incorrect
Result: Failed
Result summary for Testcase3
Adding host intents
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
Changes were found in the flow tables
Loss of dataplane connectivity detected
Leadership election tests passed( consistent view of leader across listeners and a new leader was re-elected if applicable )
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 Testcase15
Check that Leadership Election is still functional
Leadership election tests passed( consistent view of leader across listeners and a new leader was elected when the old leader resigned )
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
Switches in MN but not in ONOS:
['0000000000001000', '0000000000003004', '0000000000003015', '0000000000006000', '0000000000006018', '0000000000006022', '0000000000006023', '0000000000006024']
Switches in ONOS but not in MN:
[]
ONOS1 Switches view is incorrect
The list of ports for switch s18(0000000000006018) does not match:
The list of ports for switch s15(0000000000003015) does not match:
The list of ports for switch s4(0000000000003004) does not match:
The list of ports for switch s6(0000000000006000) does not match:
The list of ports for switch s22(0000000000006022) does not match:
The list of ports for switch s23(0000000000006023) does not match:
The list of ports for switch s24(0000000000006024) does not match:
The list of ports for switch s1(0000000000001000) does not match:
ONOS1 ports view is incorrect
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
Switches in MN but not in ONOS:
['0000000000001000', '0000000000002800', '0000000000003004', '0000000000003011', '0000000000003015', '0000000000006000', '0000000000006023']
Switches in ONOS but not in MN:
[]
ONOS1 Switches view is incorrect
The list of ports for switch s11(0000000000003011) does not match:
The list of ports for switch s15(0000000000003015) does not match:
The list of ports for switch s4(0000000000003004) does not match:
The list of ports for switch s6(0000000000006000) does not match:
The list of ports for switch s28(0000000000002800) does not match:
The list of ports for switch s1(0000000000001000) does not match:
ONOS1 ports view is incorrect
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 s5
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Switches in MN but not in ONOS:
['0000000000002800', '0000000000003011', '0000000000003015', '0000000000006000', '0000000000006007']
Switches in ONOS but not in MN:
[]
ONOS1 Switches view is incorrect
The list of ports for switch s6(0000000000006000) does not match:
The list of ports for switch s18(0000000000006018) does not match:
The list of ports for switch s11(0000000000003011) does not match:
The list of ports for switch s15(0000000000003015) does not match:
The list of ports for switch s7(0000000000006007) does not match:
The list of ports for switch s22(0000000000006022) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS1 ports view is incorrect
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 s5
Result: Pass
Result summary for Testcase8
Compare ONOS Topology view to Mininet topology
Switches in MN but not in ONOS:
['0000000000002800', '0000000000003004', '0000000000003011', '0000000000003015', '0000000000006000', '0000000000006007', '0000000000006018']
Switches in ONOS but not in MN:
[]
ONOS1 Switches view is incorrect
The list of ports for switch s6(0000000000006000) does not match:
The list of ports for switch s18(0000000000006018) does not match:
The list of ports for switch s11(0000000000003011) does not match:
The list of ports for switch s15(0000000000003015) does not match:
The list of ports for switch s4(0000000000003004) does not match:
The list of ports for switch s7(0000000000006007) does not match:
The list of ports for switch s22(0000000000006022) does not match:
The list of ports for switch s28(0000000000002800) does not match:
ONOS1 ports view is incorrect
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 HATestSingleInstanceRestart
************************************
Result summary for Testcase1
ONOS Single node cluster restart HA test - initialization
Removing raft logs
Uninstalling ONOS
commit 346609609ad1b522c8c50a0ed634c504b9408297 (HEAD, origin/master, origin/HEAD, master)
Author: Sho SHIMIZU [sshimizu@us.fujitsu.com]
AuthorDate: Thu Jan 22 17:58:44 2015 -0800
Commit: Sho SHIMIZU [sshimizu@us.fujitsu.com]
CommitDate: Thu Jan 22 17:58:44 2015 -0800
Fix typo in Javadoc comment
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 for the test to make all the cli calls to fetch the topology from each ONOS instance ): 1.9055480957 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 Testcase14
Leadership election tests passed( consistent view of leader across listeners and a leader was elected )
Result: Pass
Result summary for Testcase6
Restart ONOS node
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 for the test to make all the cli calls to fetch the topology from each ONOS instance ): 1.86114192009 seconds, 1 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 Switches was not changed
Intents are consistent across all ONOS nodes
No changes were found in the flow tables
Leadership election tests passed( consistent view of leader across listeners and a new leader was re-elected if applicable )
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 Testcase15
Check that Leadership Election is still functional
Leadership election tests passed( There is no leader after the old leader resigned )
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 for the test to make all the cli calls to fetch the topology from each ONOS instance ): 1.76333713531 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 for the test to make all the cli calls to fetch the topology from each ONOS instance ): 1.75962305069 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 s5
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 for the test to make all the cli calls to fetch the topology from each ONOS instance ): 1.76787900925 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 s5
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 for the test to make all the cli calls to fetch the topology from each ONOS instance ): 1.80301904678 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