Versions Compared

Old Version 19

changes.mady.by.user Jenkins Technical User

Saved on

compared with

New Version 20

changes.mady.by.user Jenkins Technical User

Saved on

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.2/1165/

...

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

commit 2752759c0a1401bbed9c9fdbe934437dd4fceb74 a685998d698fd9efed2352dd9bb5b6befbf370b3 (HEAD -] onos-2.2, origin/onos-2.2)
Author: Daniele Moro [daniele@opennetworking.orgAmit Ghosh [amit.ghosh@radisys.com]
AuthorDate: Mon Wed Feb 3 2312 09:3335:55 45 2020 -0800+0000
Commit: Daniele Moro [daniele@opennetworkingSaurav Das [saurav.das@opennetworking.org]
CommitDate: Fri Sat Feb 7 2115 02:5213:54 15 2020 +0000
Add support to propagate ONOS log to Kafka with KafkaAppender in log4j2
VOL-2516: Introducing meta in the ONU DS flow selector

Case 1: Switch Failure test with 2x2 Leaf-spine and 1 Onos - FAIL

...

  • 5.1 Apply cell to environment - PASS (tick)
  • 5.2 Uninstalling Atomix - PASS (tick)
  • 5.3 Uninstalling ONOS package - PASS (tick)
  • 5.4 Creating ONOS package - PASS (tick)
  • 5.5 Installing Atomix - PASS (tick)
  • 5.6 Installing ONOS package - PASS (tick)
  • 5.7 Set up ONOS secure SSH - PASS (tick)
  • 5.8 Checking ONOS service - PASS (tick)
  • 5.9 Starting ONOS CLI sessions - PASS (tick)
  • 5.10 Checking ONOS nodes - PASS (tick)
  • 5.11 Checking ONOS applications - PASS (tick)
  • 5.12 Starting Mininet Topology - PASS (tick)
  • 5.13 Check whether the flow count is bigger than 350 - FAIL (error)
    • Flow count looks wrong: 136
  • PASS (tick)
  • 5.14 Check whether all flow status are ADDED - PASS (tick)
  • 5.15 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4', u'h5', u'h6', u'h7', u'h8'] with tag CASE5 - FAIL (error)
    • IP connectivity failed
  • 5.16 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE5 - FAIL (error)
    • IP connectivity failed
  • 5.17 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE5 - FAIL (error)
    • IP connectivity failed
  • 5.18 Kill ['spine101'] - FAIL (error)
    • Failed to kill switch?
  • 5.19 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4', u'h5', u'h6', u'h7', u'h8'] with tag CASE5_Failure - FAIL (error)
    • IP connectivity failed
  • 5.20 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE5_Failure - FAIL (error)
    • IP connectivity failed
  • 5.21 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE5_Failure - FAIL (error)
    • IP connectivity failed
  • 5.22 Recovering ['spine101'] - FAIL (error)
    • Failed to recover switch?
  • 5.23 Check whether the flow count is bigger than 350 - FAIL (error)
    • Flow count looks wrong: 136
  • PASS (tick)
  • 5.24 Check whether all flow status are ADDED - PASS (tick)
  • 5.25 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4', u'h5', u'h6', u'h7', u'h8'] with tag CASE5_Recovery - FAIL (error)
    • IP connectivity failed
  • 5.26 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE5_Recovery - FAIL (error)
    • IP connectivity failed
  • 5.27 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE5_Recovery - FAIL (error)
    • IP connectivity failed
  • 5.28 Stopping Mininet - PASS (tick)
  • 5.29 Copying karaf logs - PASS (tick)