Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published from Jenkins build: https://onos-jenkins.onlab.us/job/HAClusterRestart/29/

...

commit 66f7543c6b8b65b6b914a648fd184b645a0e42f1 5939e659a41add1b7de2c6f3254fd15ce7ccabc9 (HEAD, origin/master, origin/HEAD, master)
Author: Simon Hunt [simon@onlab.us]
AuthorDate: Wed May 6 1416:0720:03 23 2015 -0700
Commit: Gerrit Code Review [gerrit@onlabSimon Hunt [simon@onlab.us]
CommitDate: Wed May 6 2116:20:17 34 2015 +0000-0700

GUI -- Made OOTB formatters and comparators final classesAdded Locale and Time Zone decorators to TimeFormatter.
HTML
<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>

...

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

Case 8: Compare ONOS Topology view to Mininet topology -

...

FAIL

  • 8.1 Create TestONTopology object - No Result (warning)
  • 8.2 Topology view is correct and consistent across all ONOS nodes - PASS (tick)FAIL (error)
  • 8.3 Checking ONOS nodes - PASS (tick)

Case 3: Adding host Intents -

...

FAIL

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

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 (tick)
    • 5.2 Get the Mastership of each switch from each controller - PASS (tick)
    • 5.3 Check for consistency in roles from each controller - PASS (tick)
    • 5.4 Get the intents from each controller - PASS (tick)
    • 5.5 Check for consistency in Intents from each controller - PASS (tick)
    • 5.6 Get the flows from each controller - PASS (tick)
    • 5.7 Check for consistency in Flows from each controller - PASS (tick)
    • 5.8 Get the OF Table entries - No Result (warning)
    • 5.9 Start continuous pings - No Result (warning)
    • 5.10 Create TestONTopology object - No Result (warning)
    • 5.11 Collecting topology information from ONOS - No Result (warning)
    • 5.12 Host view is consistent across ONOS nodes - PASS (tick)
    • 5.13 Each host has an IP address - PASS (tick)
    • 5.14 Cluster view is consistent across ONOS nodes - PASS (tick)
    • 5.15 Cluster view correct across ONOS nodes - PASS (tick)FAIL (error)
    • 5.16 Comparing ONOS topology to MN - PASS (tick)FAIL (error)

    Case 14: Start Leadership Election app - PASS

    ...

    • 6.1 Killing ONOS nodes - PASS (tick)
    • 6.2 Checking if ONOS is up yet - PASS (tick)

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

    • 8.1 Create TestONTopology object - No Result (warning)
    • 8.2 Topology view is correct and consistent across all ONOS nodes - FAIL (error)
    • 8.3 Checking ONOS nodes - PASS (tick)

    Case 3: Adding host Intents - FAIL

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

    Case 7: Running ONOS Constant State Tests - FAIL

    ...

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

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

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

      ...

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

      ...

      • 9.1 Kill Link between s3 and s28 - PASS (tick)

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

      • 8.1 Create TestONTopology object - No Result (warning)
      • 8.2 Topology view is correct and consistent across all ONOS nodes - FAIL (error)
      • 8.3 Checking ONOS nodes - PASS (tick)

      ...

      • 10.1 Bring link between s3 and s28 back up - PASS (tick)

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

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

      ...

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

      • 11.1 Kill s5 - PASS (tick)

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

      • 8.1 Create TestONTopology object - No Result (warning)
      • 8.2 Topology view is correct and consistent across all ONOS nodes - FAIL (error)
      • 8.3 Checking ONOS nodes - PASS (tick)

      ...

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

      • 12.1 Add back s5 - PASS (tick)

      Case 8: Compare ONOS Topology view to Mininet topology -

      ...

      PASS

      • 8.1 Create TestONTopology object - No Result (warning)
      • 8.2 Topology view is correct and consistent across all ONOS nodes - FAIL (error)PASS (tick)
      • 8.3 Checking ONOS nodes - PASS (tick)

      ...