Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

commit babde9cbb29f55971e7f3b25b9e35d6bf85ed4c2 581c8407e613a27aaa573a600828b30a37066fb8 (HEAD -] master, origin/master, origin/HEAD)
Author: Daniel Park pierventre [danpier@opennetworking.mcpark84@gmail.comorg]
AuthorDate: Tue Mar 9 13:37:42 2021 +0900Thu Sep 23 19:03:14 2021 +0200
Commit: Jian Li [pyguni@gmail.comPier Luigi Ventre [pier@opennetworking.org]
CommitDate: Fri Mar 12 00:48:18 Mon Sep 27 19:27:55 2021 +0000
Implement Internal Routing Capability.
[SDFAB-616] Inconsistent format of port number in DhcpRelay
--
(cherry picked from commit cc8e746f203dc457e5bb914ca4995910d7fc6e9e61bd673eec2282aff175daff141059870db78c7d)

Case 1: ONOS Failure test with 2x2

...

  • 1.1 Constructing test variables - PASS (tick)
  • 1.2 Apply cell to environment - PASS (tick)
  • 1.3 Uninstalling Atomix - PASS (tick)
  • 1.4 Uninstalling ONOS package - PASS (tick)
  • 1.5 Building ONOS Docker image - PASS (tick)
  • 1.6 Create Cluster Config - PASS (tick)
  • 1.7 Installing Atomix via docker containers - PASS (tick)
  • 1.8 Installing ONOS via docker containers - PASS (tick)
  • 1.9 Set up ONOS secure SSH - PASS (tick)
  • 1.10 Starting ONOS CLI sessions - PASS (tick)
  • 1.11 Checking ONOS nodes - PASS (tick)
  • 1.12 Checking ONOS applications - PASS (tick)
  • 1.13 Set logging levels - PASS (tick)
  • 1.14 Set ONOS configurations - PASS (tick)
  • 1.15 Starting Mininet Topology - PASS (tick)
  • 1.16 Configure switches in ONOS - PASS (tick)
  • 1.17 Check number of topology elements - PASS (tick)
  • 1.18 Check whether the flow count is >= 116 - FAIL (error)
    • Flow count looks wrong; found 0, expecting at least 116
  • 1.19 Check whether all flow status are ADDED - FAIL (error)
    • Flow status is wrong!
  • 1.20 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE1 - PASS (tick)
  • 1.21 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE1 - FAIL (error)
    • IP connectivity failed
  • 1.22 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE1 - FAIL (error)
    • IP connectivity failed
  • 1.23 Killing ONOS instances with index(es): [0] - PASS (tick)
  • 1.24 Check number of topology elements - PASS (tick)
  • 1.25 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE1_Failure - PASS (tick)
  • 1.26 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE1_Failure - FAIL (error)
    • IP connectivity failed
  • 1.27 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE1_Failure - FAIL (error)
    • IP connectivity failed
  • 1.28 Recovering ONOS instances with index(es): [0] - PASS (tick)
  • 1.29 Checking if ONOS CLI is ready - PASS (tick)
  • 1.30 Checking ONOS nodes - PASS (tick)
  • 1.31 Check number of topology elements - PASS (tick)
  • 1.32 Check whether the flow count is >= 116 - FAIL (error)
    • Flow count looks wrong; found 0, expecting at least 116
  • 1.33 Check whether all flow status are ADDED - FAIL (error)
    • Flow status is wrong!
  • 1.34 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE1_Recovery - PASS (tick)
  • 1.35 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE1_Recovery - FAIL (error)
    • IP connectivity failed
  • 1.36 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE1_Recovery - FAIL (error)
    • IP connectivity failed
  • 1.37 Check number of topology elements - PASS (tick)
  • 1.38 Stopping Mininet - PASS (tick)
  • 1.39 Copying karaf logs - PASS (tick)

...

leaf-spine topology - FAIL