View Source

HATestClusterRestart at 06 May 2015 17:44:54

commit 5939e659a41add1b7de2c6f3254fd15ce7ccabc9 (HEAD, origin/master, origin/HEAD, master)
Author: Simon Hunt [simon@onlab.us]
AuthorDate: Wed May 6 16:20:23 2015 -0700
Commit: Simon Hunt [simon@onlab.us]
CommitDate: Wed May 6 16:20:34 2015 -0700

GUI -- Added Locale and Time Zone decorators to TimeFormatter.

<iframe src="https://onos-jenkins.onlab.us/job/HAClusterRestart/plot/getPlot?index=0&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

Case 1: Setting up test environment - PASS

1.1 Applying cell variable to environment - No Result
1.2 Starting Mininet - PASS
1.3 Compiling the latest version of ONOS - No Result
1.4 Creating ONOS package - PASS
1.5 Installing ONOS package - PASS
1.6 Checking if ONOS is up yet - PASS
1.7 Start Packet Capture MN - No Result
1.8 App Ids check - PASS

Case 2: Assigning Controllers - PASS

2.1 Assign switches to controllers - PASS
2.2 Assign mastership of switches to specific controllers - PASS
2.3 Check mastership was correctly assigned - PASS

Case 8: Compare ONOS Topology view to Mininet topology - FAIL

8.1 Create TestONTopology object - No Result
8.2 Topology view is correct and consistent across all ONOS nodes - FAIL
8.3 Checking ONOS nodes - PASS

Case 3: Adding host Intents - FAIL

3.1 Install reactive forwarding app - PASS
3.2 Check app ids - PASS
3.3 Discovering Hosts( Via pingall for now ) - FAIL
3.4 Uninstall reactive forwarding app - PASS
3.5 Check app ids - PASS
3.6 Add host intents via cli - PASS
3.7 Intent Anti-Entropy dispersion - PASS

Case 4: Ping across added host intents - PASS

Case 5: Setting up and gathering data for current state - FAIL

5.1 Check that each switch has a master - PASS
5.2 Get the Mastership of each switch from each controller - PASS
5.3 Check for consistency in roles from each controller - PASS
5.4 Get the intents from each controller - PASS
5.5 Check for consistency in Intents from each controller - PASS
5.6 Get the flows from each controller - PASS
5.7 Check for consistency in Flows from each controller - PASS
5.8 Get the OF Table entries - No Result
5.9 Start continuous pings - No Result
5.10 Create TestONTopology object - No Result
5.11 Collecting topology information from ONOS - No Result
5.12 Host view is consistent across ONOS nodes - PASS
5.13 Each host has an IP address - PASS
5.14 Cluster view is consistent across ONOS nodes - PASS
5.15 Cluster view correct across ONOS nodes - FAIL
5.16 Comparing ONOS topology to MN - FAIL

Case 14: Start Leadership Election app - PASS

14.1 Install leadership election app - PASS
14.2 Run for election on each node - PASS
14.3 Check that each node shows the same leader - PASS

Case 16: Install Primitives app - PASS

16.1 Install Primitives app - PASS

Case 17: Check for basic functionality with distributed primitives - PASS

Test the methods of the distributed primitives (counters and sets) throught the cli

17.1 Increment and get a default counter on each node - PASS
17.2 Increment and get an in memory counter on each node - PASS
17.3 Check counters are consistant across nodes - PASS
17.4 Counters we added have the correct values - PASS
17.5 Distributed Set get - PASS
17.6 Distributed Set size - PASS
17.7 Distributed Set add() - PASS
17.8 Distributed Set addAll() - PASS
17.9 Distributed Set contains() - PASS
17.10 Distributed Set containsAll() - PASS
17.11 Distributed Set remove() - PASS
17.12 Distributed Set removeAll() - PASS
17.13 Distributed Set addAll() - PASS
17.14 Distributed Set clear() - PASS
17.15 Distributed Set addAll() - PASS
17.16 Distributed Set retain() - PASS

Case 6: Restart entire ONOS cluster - PASS

6.1 Killing ONOS nodes - PASS
6.2 Checking if ONOS is up yet - PASS

Case 8: Compare ONOS Topology view to Mininet topology - FAIL

8.1 Create TestONTopology object - No Result
8.2 Topology view is correct and consistent across all ONOS nodes - FAIL
8.3 Checking ONOS nodes - PASS

Case 3: Adding host Intents - FAIL

3.1 Install reactive forwarding app - PASS
3.2 Check app ids - PASS
3.3 Discovering Hosts( Via pingall for now ) - FAIL
3.4 Uninstall reactive forwarding app - PASS
3.5 Check app ids - PASS
3.6 Add host intents via cli - FAIL
3.7 Intent Anti-Entropy dispersion - PASS

Case 7: Running ONOS Constant State Tests - FAIL

7.1 Check that each switch has a master - PASS
7.2 Read device roles from ONOS - PASS
7.3 Check for consistency in roles from each controller - PASS
7.4 Compare switch roles from before failure - FAIL
7.5 Get the intents and compare across all nodes - PASS
7.6 Check for consistency in Intents from each controller - FAIL
7.7 Get the OF Table entries and compare to before component failure - FAIL
7.8 Check the continuous pings to ensure that no packets were dropped during component failure - FAIL

Case 4: Ping across added host intents - PASS

Case 15: Check that Leadership Election is still functional - FAIL

15.1 Run for election on each node - PASS
15.2 Check that each node shows the same leader - PASS
15.3 Find current leader and withdraw - PASS
15.4 Make sure new leader is elected - FAIL
15.5 Run for election on old leader( just so everyone is in the hat ) - PASS
15.6 Leader did not change when old leader re-ran - FAIL

Case 17: Check for basic functionality with distributed primitives - FAIL

Test the methods of the distributed primitives (counters and sets) throught the cli

17.1 Increment and get a default counter on each node - PASS
17.2 Increment and get an in memory counter on each node - PASS
17.3 Check counters are consistant across nodes - FAIL
17.4 Counters we added have the correct values - FAIL
17.5 Distributed Set get - FAIL
17.6 Distributed Set size - FAIL
17.7 Distributed Set add() - FAIL
17.8 Distributed Set addAll() - PASS
17.9 Distributed Set contains() - PASS
17.10 Distributed Set containsAll() - PASS
17.11 Distributed Set remove() - FAIL
17.12 Distributed Set removeAll() - PASS
17.13 Distributed Set addAll() - PASS
17.14 Distributed Set clear() - PASS
17.15 Distributed Set addAll() - PASS
17.16 Distributed Set retain() - PASS

Case 9: Turn off a link to ensure that Link Discovery is working properly - PASS

9.1 Kill Link between s3 and s28 - PASS

Case 8: Compare ONOS Topology view to Mininet topology - FAIL

8.1 Create TestONTopology object - No Result
8.2 Topology view is correct and consistent across all ONOS nodes - FAIL
8.3 Checking ONOS nodes - PASS

Case 4: Ping across added host intents - PASS

Case 10: Restore a link to ensure that Link Discovery is working properly - PASS

10.1 Bring link between s3 and s28 back up - PASS

Case 8: Compare ONOS Topology view to Mininet topology - PASS

8.1 Create TestONTopology object - No Result
8.2 Topology view is correct and consistent across all ONOS nodes - PASS
8.3 Checking ONOS nodes - PASS

Case 4: Ping across added host intents - PASS

Case 11: Killing a switch to ensure it is discovered correctly - PASS

11.1 Kill s5 - PASS

Case 8: Compare ONOS Topology view to Mininet topology - FAIL

8.1 Create TestONTopology object - No Result
8.2 Topology view is correct and consistent across all ONOS nodes - FAIL
8.3 Checking ONOS nodes - PASS

Case 4: Ping across added host intents - PASS

Case 12: Adding a switch to ensure it is discovered correctly - PASS

12.1 Add back s5 - PASS

Case 8: Compare ONOS Topology view to Mininet topology - PASS

8.1 Create TestONTopology object - No Result
8.2 Topology view is correct and consistent across all ONOS nodes - PASS
8.3 Checking ONOS nodes - PASS

Case 4: Ping across added host intents - PASS

Case 13: Test Cleanup - PASS

13.1 Killing tcpdumps - No Result
13.2 Copying MN pcap and ONOS log files to test station - No Result
13.3 Stopping Mininet - PASS
13.4 Checking ONOS Logs for errors - No Result
13.5 Packing and rotating pcap archives - No Result