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/Pipeline_postjob_BM/2274/

...

...

HTML

<img src="https://onos-jenkins.onlab.us/job/Pipeline_postjob_BM/lastSuccessfulBuild/artifact/SRClusterRestart_onos-1.11_20-builds_graph.jpg", alt="SRClusterRestart", style="width:525px;height:350px;border:0">

commit ba7eb1afc0e3a71f6cf03fdf263e935feb60613d commit 4b013201105ff57da6979d2f9b4544fd73362822 (HEAD, origin/onos-1.11, onos-1.11)
Author: Yi Tseng [yi@opennetworking.orgSaurav Das [sauravdas@alumni.stanford.edu]
AuthorDate: Fri Sep 8 17:22:51 2017 -0700Wed Dec 13 16:19:35 2017 -0800
Commit: Yi Tseng [yi@opennetworking.org]
CommitDate: Tue Sep 12 17:26:56 2017 -0700
[CORD-1887] Make DHCP relay works with dual homing

Case 1: Copy karaf logs - FAIL

Copying the karaf logs to preserve them throughreinstalling ONOS

  • 1.1 Constructing test variables - No Result (warning)
  • 1.2 Constructing test variables - PASS (tick)
  • 1.3 Apply cell to environment - PASS (tick)
  • 1.4 Creating ONOS package - PASS (tick)
  • 1.5 Installing ONOS package - PASS (tick)
  • 1.6 Set up ONOS secure SSH - PASS (tick)
  • 1.7 Checking ONOS service - PASS (tick)
  • 1.8 Checking if ONOS CLI is ready - PASS (tick)
  • 1.9 Starting Mininet Topology - PASS (tick)
  • 1.10 Check whether the flow count is bigger than 116 - FAIL (error)
    • Flow count looks wrong: False
  • 1.11 Check whether all flow status are ADDED - PASS (tick)
  • 1.12 Connectivity for [u'h1', u'h2', u'h3', u'h4'] CASE1 - FAIL (error)
    • IP connectivity failed
  • 1.13 Connectivity for [u'olt10', u'vsg10'] CASE1 - FAIL (error)
    • IP connectivity failed
  • 1.14 Connectivity for [u'olt5', u'vsg5'] CASE1 - FAIL (error)
    • IP connectivity failed
  • 1.15 Killing ONOS instance - PASS (tick)
  • 1.16 Connectivity for [u'h1', u'h2', u'h3', u'h4'] CASE1_Failure - FAIL (error)
    • IP connectivity failed
  • 1.17 Connectivity for [u'olt10', u'vsg10'] CASE1_Failure - FAIL (error)
    • IP connectivity failed
  • 1.18 Connectivity for [u'olt5', u'vsg5'] CASE1_Failure - FAIL (error)
    • IP connectivity failed
  • 1.19 Recovering ONOS instance - PASS (tick)
  • 1.20 Checking if ONOS CLI is ready - PASS (tick)
  • 1.21 Checking if ONOS CLI is ready - PASS (tick)
  • 1.22 Checking if ONOS CLI is ready - PASS (tick)
  • 1.23 Checking ONOS nodes - PASS (tick)
  • 1.24 Check whether the flow count is bigger than 116 - FAIL (error)
    • Flow count looks wrong: False
  • 1.25 Check whether all flow status are ADDED - PASS (tick)
  • 1.26 Connectivity for [u'h1', u'h2', u'h3', u'h4'] CASE1_Failure - FAIL (error)
    • IP connectivity failed
  • 1.27 Connectivity for [u'olt10', u'vsg10'] CASE1_Failure - FAIL (error)
    • IP connectivity failed
  • 1.28 Connectivity for [u'olt5', u'vsg5'] CASE1_Failure - FAIL (error)
    • IP connectivity failed
  • 1.29 Stopping Mininet - PASS (tick)
  • 1.30 Copying karaf logs - PASS (tick)

Case 2: Copy karaf logs - FAIL

Copying the karaf logs to preserve them throughreinstalling ONOS

  • 2.1 Apply cell to environment - PASS (tick)
  • 2.2 Creating ONOS package - PASS (tick)
  • 2.3 Installing ONOS package - PASS (tick)
  • 2.4 Set up ONOS secure SSH - PASS (tick)
  • 2.5 Checking ONOS service - PASS (tick)
  • 2.6 Checking if ONOS CLI is ready - PASS (tick)
  • 2.7 Starting Mininet Topology - PASS (tick)
  • 2.8 Check whether the flow count is bigger than 350 - FAIL (error)
    • Flow count looks wrong: False
  • 2.9 Check whether all flow status are ADDED - PASS (tick)
  • 2.10 Connectivity for [u'h1', u'h2', u'h3', u'h4', u'h5', u'h6', u'h7', u'h8'] CASE2 - FAIL (error)
    • IP connectivity failed
  • 2.11 Connectivity for [u'olt10', u'vsg10'] CASE2 - FAIL (error)
    • IP connectivity failed
  • 2.12 Connectivity for [u'olt5', u'vsg5'] CASE2 - FAIL (error)
    • IP connectivity failed
  • 2.13 Killing ONOS instance - PASS (tick)
  • 2.14 Connectivity for [u'h1', u'h2', u'h3', u'h4', u'h5', u'h6', u'h7', u'h8'] CASE2_Failure - FAIL (error)
    • IP connectivity failed
  • 2.15 Connectivity for [u'olt10', u'vsg10'] CASE2_Failure - FAIL (error)
    • IP connectivity failed
  • 2.16 Connectivity for [u'olt5', u'vsg5'] CASE2_Failure - FAIL (error)
    • IP connectivity failed
  • 2.17 Recovering ONOS instance - PASS (tick)
  • 2.18 Checking if ONOS CLI is ready - PASS (tick)
  • 2.19 Checking if ONOS CLI is ready - PASS (tick)
  • 2.20 Checking if ONOS CLI is ready - PASS (tick)
  • 2.21 Checking ONOS nodes - PASS (tick)
  • 2.22 Check whether the flow count is bigger than 350 - FAIL (error)
    • Flow count looks wrong: False
  • 2.23 Check whether all flow status are ADDED - PASS (tick)
  • 2.24 Connectivity for [u'h1', u'h2', u'h3', u'h4', u'h5', u'h6', u'h7', u'h8'] CASE3_Recovery - FAIL (error)
    • IP connectivity failed
  • 2.25 Connectivity for [u'olt10', u'vsg10'] CASE3_Recovery - FAIL (error)
    • IP connectivity failed
  • 2.26 Connectivity for [u'olt5', u'vsg5'] CASE3_Recovery - FAIL (error)
    • IP connectivity failed
  • 2.27 Stopping Mininet - PASS (tick)
  • 2.28 Copying karaf logs - PASS (tick)

Case 3: Copy karaf logs - FAIL

Copying the karaf logs to preserve them throughreinstalling ONOS

...

  • Flow count looks wrong: False

...

  • IP connectivity failed

...

  • IP connectivity failed

...

  • IP connectivity failed

...

  • IP connectivity failed

...

  • IP connectivity failed

...

  • IP connectivity failed

...

  • Flow count looks wrong: False

...

  • IP connectivity failed

...

  • IP connectivity failed

...

  • IP connectivity failed

...

Saurav Das [sauravdas@alumni.stanford.edu]
CommitDate: Wed Dec 13 16:19:35 2017 -0800

Bug fix for IgnoreDhcp rules after switch restart. Also fixed NPE in group handler,

Case 1: Pull onos branch and build onos on Teststation. - FAIL

...