Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published from Jenkins build: https://jenkins.onosproject.org/job/SR-pipeline-2.0/1055/

...

HTML
<img src="https://jenkins.onosproject.org/view/QA/job/postjob-Fabric3/lastSuccessfulBuild/artifact/SROnosFailure_onos-2.0_20-builds_graph.jpg", alt="SROnosFailure", style="width:525px;height:350px;border:0">

commit f40d2d42352bd657fa4124fb7ba4171d0d61a2fe 5cd58140a9d0909a62c0072a5e7070315ba6acd3 (HEAD -] onos-2.0, origin/onos-2.0)
Author: Ray Milkey [ray@opennetworking.orgHarshada Chaundkar [Harshada_Chaundkar@comcast.com]
AuthorDate: Fri Mon Feb 15 1018 12:0027:57 34 2019 -08000500
Commit: Ray Milkey Charles Chan [ray@opennetworkingrascov@gmail.orgcom]
CommitDate: Fri Wed Feb 20 15 12:4219:22 33 2019 -0800
Change JDK container for Docker build
Potential Null Pointer Exception fix for Cpman, Groups , Flows and Mastership API

Case 1: ONOS Failure test with 2x2 Leaf-spine - FAIL

...

  • 2.1 Apply cell to environment - PASS (tick)
  • 2.2 Uninstalling Atomix - PASS (tick)
  • 2.3 Uninstalling ONOS package - PASS (tick)
  • 2.4 Creating ONOS package - PASS (tick)
  • 2.5 Installing Atomix - PASS (tick)
  • 2.6 Installing ONOS package - PASS (tick)
  • 2.7 Set up ONOS secure SSH - PASS (tick)
  • 2.8 Checking ONOS service - PASS (tick)
  • 2.9 Starting ONOS CLI sessions - PASS (tick)
  • 2.10 Checking ONOS nodes - PASS (tick)
  • 2.11 Checking ONOS applications - PASS (tick)
  • 2.12 Starting Mininet Topology - PASS (tick)
  • 2.13 Check whether the flow count is bigger than 350 - FAIL (error)
    • Flow count looks wrong: 24
  • PASS (tick)
  • 2.14 Check whether all flow status are ADDED - PASS (tick)
  • 2.15 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4', u'h5', u'h6', u'h7', u'h8'] with tag CASE2 - FAIL (error)
    • IP connectivity failed
  • 2.16 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE2 - FAIL (error)
  • IP connectivity failed
  • PASS (tick)
  • 2.17 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE2 - FAIL (error)
    • IP connectivity failed
  • PASS (tick)
  • 2.18 Killing ONOS instances with index(es): [0] - PASS (tick)
  • 2.19 Check number of topology elements - FAIL (error)
    • Unexpected number of links, switches, and/or controllers
  • 2.20 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4', u'h5', u'h6', u'h7', u'h8'] with tag CASE2_Failure - FAIL (error)
    • IP connectivity failed
  • 2.21 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE2_Failure - FAIL (error)
  • IP connectivity failed
  • PASS (tick)
  • 2.22 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE2_Failure - FAIL (error)
    • IP connectivity failed
  • PASS (tick)
  • 2.23 Recovering ONOS instances with index(es): [0] - PASS (tick)
  • 2.24 Checking if ONOS CLI is ready - PASS (tick)
  • 2.25 Checking ONOS nodes - PASS (tick)
  • 2.26 Check number of topology elements - PASS (tick)
  • 2.27 Check whether the flow count is bigger than 350 - FAIL (error)
  • Flow count looks wrong: 24
  • PASS (tick)
  • 2.28 Check whether all flow status are ADDED - PASS (tick)
  • 2.29 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4', u'h5', u'h6', u'h7', u'h8'] with tag CASE2_Recovery - FAIL (error)
    • IP connectivity failed
  • 2.30 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE2_Recovery - FAIL (error)
    • IP connectivity failed
  • PASS (tick)
  • 2.31 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE2_Recovery - FAIL (error)
  • IP connectivity failed
  • PASS (tick)
  • 2.32 Stopping Mininet - PASS (tick)
  • 2.33 Copying karaf logs - PASS (tick)

...