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

...

commit ad75aa2027f9ea219f2cdbb6fcbe3210119d25e1 3e1bac23ed96d242a1393edd2dfb644b08e2a190 (HEAD, origin/master, origin/HEAD, master)
Author: Steven Burrows [sburrows@villa-technologiesJian Li [pyguni@gmail.com]
AuthorDate: Wed Tue Dec 14 176 02:1708:24 12 2016 -0500+0900
Commit: Simon Hunt Jian Li [simon@onlabpyguni@gmail.uscom]
CommitDate: Wed Fri Dec 14 2216 16:3952:37 47 2016 +0000
Topo2: Fixed instance device count and mastership
Add ReplyRecord field into Map-Request message
HTML
<iframe src="https://onos-jenkins.onlab.us/job/HAclusterRestart/plot/Plot-HA/getPlot?index=2&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

...

  • 8.1 Comparing ONOS topology to MN topology - PASS (tick)
  • 8.2 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.3 Hosts information is correct - PASS (tick)
  • 8.4 Host attachment points to the network - PASS (tick)
  • 8.5 Clusters view is consistent across all ONOS nodes - PASS (tick)
  • 8.6 There is only one SCC - PASS (tick)
  • 8.7 Device information is correct - PASS (tick)
  • 8.8 Links are correct - PASS (tick)
  • 8.9 Hosts are correct - PASS (tick)
  • 8.10 Checking ONOS nodes - PASS (tick)

Case 4: Verify connectivity by sending traffic across Intents -

...

FAIL

Ping across added host intents to check functionality and check the state of the intent

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

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

...

No Result

  • 5.1 Check that each switch has a master - PASS (tick)FAIL (error)
    • Some devices don't have a master assigned
  • 5.2 Get the Mastership of each switch from each controller - PASS (tick)FAIL (error)
    • Error in reading roles from ONOS
  • 5.3 Check for consistency in roles from each controller - PASS (tick)FAIL (error)
    • ONOS nodes have different views of switch roles
  • 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 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)

Case 14: Start Leadership Election app - FAIL

  • 14.1 Install leadership election app - PASS (tick)
  • 14.2 Run for election on each node - FAIL (error)
    • Inconsistent leaderboards

Case 16: Install Primitives app - PASS

  • FAIL (error)
    • Error in reading intents from ONOS
    16.1 Install Primitives app - PASS (tick)