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/82/

...

commit 70aaa1b9310659c6b43dbdf6f8b0255af36dcd7e a9c18b9ba3001f940e03ba3cabeda2f159198584 (HEAD, origin/master, origin/HEAD, master)
Author: alshabib [alshabibi.ali@gmail.comBrian O'Connor [bocon@onlab.us]
AuthorDate: Fri Mon Sep 25 1428 16:3003:59 43 2015 -0700
Commit: Gerrit Code Review [gerrit@onlabBrian O'Connor [bocon@onlab.us]
CommitDate: Sun Mon Sep 27 28 16:08:52:08 2015 +0000
adding device specific counters for meter ids in01 2015 -0700

ONOS-2979 ObjectiveTracker improvements
HTML
<iframe src="https://onos-jenkins.onlab.us/job/HAclusterRestart/plot/Plot-HA/getPlot?index=0&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

...

  • 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)
    • Reactive Pingall failed, one or more ping pairs failed
  • PASS (tick)
  • 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)-Entropy dispersion - FAIL (error)
    • Intent ECM anti-entropy took too long

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

...

  • 4.1 Ping across added host intents - PASS (tick)
  • 4.2 Check Intent state - PASS (tick)
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - PASS (tick)

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

...

PASS

  • 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 - FAIL (error)
  • ONOS nodes have different views of intents
  • 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 Collecting topology information from ONOS - No Result (warning)
  • 5.11 Host view is consistent across ONOS nodes - PASS (tick)
  • 5.12 Each host has an IP address - PASS (tick)
  • 5.13 Cluster view is consistent across ONOS nodes - PASS (tick)
  • 5.14 Cluster view correct across ONOS nodes - PASS (tick)
  • 5.15 Comparing ONOS topology to MN - PASS (tick)
  • 5.16 Device information is correct - PASS (tick)
  • 5.17 Links are correct - PASS (tick)
  • 5.18 Hosts are correct - PASS (tick)

...

  • 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)
    • Reactive Pingall failed, one or more ping pairs failed
  • 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)- FAIL (error)
    • Intent ECM anti-entropy took too long

Case 7: Running ONOS Constant State Tests - FAIL

...

  • 17.1 Increment then get a default counter on each node - FAIL (error)
    • Error incrementing default counter
  • 17.2 Get then Increment a default counter on each node - FAIL (error)
    • Error incrementing default counter
  • 17.3 Counters we added have the correct values - FAIL (error)
  • Added counters are incorrect
  • PASS (tick)
  • 17.4 Add -8 to then get a default counter on each node - FAIL (error)
    • Error incrementing default counter
  • 17.5 Add 5 to then get a default counter on each node - FAIL (error)
    • Error incrementing default counter
  • 17.6 Get then add 5 to a default counter on each node - FAIL (error)
    • Error incrementing default counter
  • 17.7 Counters we added have the correct values - FAIL (error)
    • Added counters are incorrect
  • 17.8 Increment and get an in-memory counter on each node - PASS (tick)
  • 17.9 Get then Increment a in-memory counter on each node - PASS (tick)
  • 17.10 Counters we added have the correct values - PASS (tick)
  • 17.11 Add -8 to then get a in-memory counter on each node - FAIL (error)
    • Error incrementing in-memory counter
  • 17.12 Add 5 to then get a in-memory counter on each node - FAIL (error)
    • Error incrementing in-memory counter
  • 17.13 Get then add 5 to a in-memory counter on each node - PASS (tick)
  • 17.14 Counters we added have the correct values - PASS (tick)
  • 17.15 Check counters are consistant across nodes - PASS (tick)
  • 17.16 Counters we added have the correct values - PASS (tick)
  • 17.17 Distributed Set get - PASS (tick)
  • 17.18 Distributed Set size - PASS (tick)
  • 17.19 Distributed Set add() - FAIL (error)
  • Set add was incorrect
  • PASS (tick)
  • 17.20 Distributed Set addAll() - FAIL (error) Set addAll
  • was incorrect
  • () - PASS (tick)
  • 17.21 Distributed Set contains() - PASS (tick)
  • 17.22 Distributed Set containsAll() - PASS (tick)
  • 17.23 Distributed Set remove() - FAIL (error)
  • Set remove was incorrect
  • PASS (tick)
  • 17.24 Distributed Set removeAll() - FAIL (error)
  • Set removeAll was incorrect
  • PASS (tick)
  • 17.25 Distributed Set addAll() - PASS (tick)
  • 17.26 Distributed Set clear() - PASS (tick)
  • 17.27 Distributed Set addAll() - PASS (tick)
  • 17.28 Distributed Set retain() - PASS (tick)
  • 17.29 Partitioned Transactional maps put - PASS (tick)
  • 17.30 Partitioned Transactional maps get - PASS (tick)
  • 17.31 In-memory Transactional maps put - PASS (tick)
  • 17.32 In-Memory Transactional maps get - PASS (tick)

...

  • 4.1 Ping across added host intents - FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • 4.2 Check Intent state - PASS (tick)FAIL (error)
    • Intents are not all in INSTALLED state
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - FAIL (error)
    • Intents have not been installed correctly, pings failed.

...

  • 4.1 Ping across added host intents - FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • 4.2 Check Intent state - FAIL (error)
    • Intents are not all in INSTALLED state
  • PASS (tick)
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - FAIL (error)
    • Intents have not been installed correctly, pings failed.

Case 13: Test Cleanup - PASS

  • 13.1 Killing tcpdumps - No Result (warning)
  • 13.2 Copying MN pcap and ONOS log files to test station - No Result (warning)
  • 13.2 3 Stopping Mininet - PASS (tick)
  • 13.3 4 Checking ONOS Logs for errors - No Result (warning)