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/HAswapNodes/571/

...

commit 1169c95d894f519c1ad881fd86cf217342e941bc 10517fde1c3158a1c70e3138dcb3e88633db5e72 (HEAD, origin/master, origin/HEAD, master)
Author: Simon Hunt [simon@onlab.usYuta HIGUCHI [y-higuchi@ak.jp.nec.com]
AuthorDate: Mon Wed Jun 5 117 09:2034:11 31 2017 -0700
Commit: Simon Hunt Thomas Vachuska [simon@onlabtom@onlab.us]
CommitDate: Tue Wed Jun 6 177 20:2118:48 22 2017 -0700
OS-1 : insecure UI websocket.+0000

Minor fixes to OvsdbDeviceProviderTest
HTML
<iframe src="https://onos-jenkins.onlab.us/job/HAswapNodes/plot/Plot-HA/getPlot?index=2&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 - FAIL (error)
  • Something is wrong with 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 - FAIL (error)

Case 7: Running ONOS Constant State Tests -

...

No Result

  • 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 Get the intents and compare across all nodes - PASS (tick)
  • 7.5 Check for consistency in Intents from each controller - FAIL (error)
    • ONOS nodes have different views of intents
  • 7.6 Compare current intents with intents before the scaling - FAIL (error)
    • The Intents changed during scaling
  • 7.7 Get the OF Table entries and compare to before component scaling - FAIL (error)
    • Changes were found in the flow tables
  • 7.8 Leadership Election is still functional - FAIL (error)
    • Something went wrong with Leadership election

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 - FAIL (error)
    • Intents are not all in INSTALLED state
  • 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)

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

  • FAIL (error)
    • Error in reading intents from ONOS
  • 15.1 Run for election on each node - PASS (tick)
  • 15.2 Check that each node shows the same leader and candidates - FAIL (error)
    • Nodes have different leaderboards
  • 15.3 Find current leader and withdraw - FAIL (error)
    • Node was not withdrawn from election
  • 15.4 Check that a new node was elected leader - FAIL (error)
    • Something went wrong with Leadership election
  • 15.5 Check that that new leader was the candidate of old leader - FAIL (error)
    • Incorrect Candidate Elected
  • 15.6 Run for election on old leader( just so everyone is in the hat ) - FAIL (error)
    • App failed to run for election
  • 15.7 Check that oldLeader is a candidate, and leader if only 1 node - FAIL (error)
    • Something went wrong with Leadership election after the old leader re-ran for election