Have questions? Stuck? Please check our FAQ for some common questions and answers.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 69 Next »

SROnosFailure at 03 Apr 2021 07:21:50

SROnosFailure-stratum

commit 2b4de873e4033b7973b399d25cb8828a73bc2e24 (HEAD -] master, origin/master, origin/HEAD)
Author: Thomas Vachuska [tom@opennetworking.org]
AuthorDate: Tue Mar 30 16:31:34 2021 -0700
Commit: Charles Chan [charles@opennetworking.org]
CommitDate: Fri Apr 2 07:12:47 2021 +0000

Added mechanism for apps to easily add their own custom link/node/host highlighting wihout having to create a new UI extensions

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

  • 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 - FAIL (error)
    • IP connectivity failed
  • 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 - FAIL (error)
    • IP connectivity failed
  • 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 - FAIL (error)
    • IP connectivity failed
  • 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)

Case 2: ONOS Failure test with 4x4 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 Building ONOS Docker image - PASS (tick)
  • 2.5 Create Cluster Config - PASS (tick)
  • 2.6 Installing Atomix via docker containers - PASS (tick)
  • 2.7 Installing ONOS via docker containers - PASS (tick)
  • 2.8 Set up ONOS secure SSH - 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 Set logging levels - PASS (tick)
  • 2.13 Set ONOS configurations - PASS (tick)
  • 2.14 Starting Mininet Topology - PASS (tick)
  • 2.15 Configure switches in ONOS - PASS (tick)
  • 2.16 Check number of topology elements - FAIL (error)
    • Unexpected number of links, switches, and/or controllers: The number of links, switches, nodes, and SCCs does not match what was expected
    • ONOS sees 8 devices (8 expected) and 8 links (32 expected) and 3 controllers (3 expected) and 8 SCCs (1 expected)
  • 2.17 Check whether the flow count is >= 350 - FAIL (error)
    • Flow count looks wrong; found 0, expecting at least 350
  • 2.18 Check whether all flow status are ADDED - FAIL (error)
    • Flow status is wrong!
  • 2.19 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.20 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE2 - FAIL (error)
    • IP connectivity failed
  • 2.21 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE2 - FAIL (error)
    • IP connectivity failed
  • 2.22 Killing ONOS instances with index(es): [0] - PASS (tick)
  • 2.23 Check number of topology elements - FAIL (error)
    • Unexpected number of links, switches, and/or controllers: The number of links, switches, nodes, and SCCs does not match what was expected
    • ONOS sees 8 devices (8 expected) and 8 links (32 expected) and 2 controllers (2 expected) and 8 SCCs (1 expected)
  • 2.24 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.25 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE2_Failure - FAIL (error)
    • IP connectivity failed
  • 2.26 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE2_Failure - FAIL (error)
    • IP connectivity failed
  • 2.27 Recovering ONOS instances with index(es): [0] - PASS (tick)
  • 2.28 Checking if ONOS CLI is ready - PASS (tick)
  • 2.29 Checking ONOS nodes - PASS (tick)
  • 2.30 Check number of topology elements - PASS (tick)
  • 2.31 Check whether the flow count is >= 350 - FAIL (error)
    • Flow count looks wrong; found 0, expecting at least 350
  • 2.32 Check whether all flow status are ADDED - FAIL (error)
    • Flow status is wrong!
  • 2.33 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.34 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE2_Recovery - FAIL (error)
    • IP connectivity failed
  • 2.35 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE2_Recovery - FAIL (error)
    • IP connectivity failed
  • 2.36 Check number of topology elements - FAIL (error)
    • Unexpected number of links, switches, and/or controllers: The number of links, switches, nodes, and SCCs does not match what was expected
    • ONOS sees 8 devices (8 expected) and 8 links (32 expected) and 3 controllers (3 expected) and 8 SCCs (1 expected)
  • 2.37 Stopping Mininet - PASS (tick)
  • 2.38 Copying karaf logs - PASS (tick)

Case 3: ONOS Failure test with single switch - FAIL

  • 3.1 Apply cell to environment - PASS (tick)
  • 3.2 Uninstalling Atomix - PASS (tick)
  • 3.3 Uninstalling ONOS package - PASS (tick)
  • 3.4 Building ONOS Docker image - PASS (tick)
  • 3.5 Create Cluster Config - PASS (tick)
  • 3.6 Installing Atomix via docker containers - PASS (tick)
  • 3.7 Installing ONOS via docker containers - PASS (tick)
  • 3.8 Set up ONOS secure SSH - PASS (tick)
  • 3.9 Starting ONOS CLI sessions - PASS (tick)
  • 3.10 Checking ONOS nodes - PASS (tick)
  • 3.11 Checking ONOS applications - PASS (tick)
  • 3.12 Set logging levels - PASS (tick)
  • 3.13 Set ONOS configurations - PASS (tick)
  • 3.14 Starting Mininet Topology - PASS (tick)
  • 3.15 Configure switches in ONOS - PASS (tick)
  • 3.16 Check number of topology elements - PASS (tick)
  • 3.17 Check whether the flow count is >= 15 - FAIL (error)
    • Flow count looks wrong; found 0, expecting at least 15
  • 3.18 Check whether all flow status are ADDED - FAIL (error)
    • Flow status is wrong!
  • 3.19 Verify full connectivity for [u'h1', u'h2'] with tag CASE3 - PASS (tick)
  • 3.20 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE3 - FAIL (error)
    • IP connectivity failed
  • 3.21 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE3 - FAIL (error)
    • IP connectivity failed
  • 3.22 Verify full connectivity for [u'olt1', u'vsg1'] with tag CASE3 - FAIL (error)
    • IP connectivity failed
  • 3.23 Killing ONOS instances with index(es): [0] - PASS (tick)
  • 3.24 Check number of topology elements - PASS (tick)
  • 3.25 Verify full connectivity for [u'h1', u'h2'] with tag CASE3_Failure - PASS (tick)
  • 3.26 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE3_Failure - FAIL (error)
    • IP connectivity failed
  • 3.27 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE3_Failure - FAIL (error)
    • IP connectivity failed
  • 3.28 Verify full connectivity for [u'olt1', u'vsg1'] with tag CASE3_Failure - FAIL (error)
    • IP connectivity failed
  • 3.29 Recovering ONOS instances with index(es): [0] - PASS (tick)
  • 3.30 Checking if ONOS CLI is ready - PASS (tick)
  • 3.31 Checking ONOS nodes - PASS (tick)
  • 3.32 Check number of topology elements - PASS (tick)
  • 3.33 Check whether the flow count is >= 15 - FAIL (error)
    • Flow count looks wrong; found 0, expecting at least 15
  • 3.34 Check whether all flow status are ADDED - FAIL (error)
    • Flow status is wrong!
  • 3.35 Verify full connectivity for [u'h1', u'h2'] with tag CASE3_Recovery - PASS (tick)
  • 3.36 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE3_Recovery - FAIL (error)
    • IP connectivity failed
  • 3.37 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE3_Recovery - FAIL (error)
    • IP connectivity failed
  • 3.38 Verify full connectivity for [u'olt1', u'vsg1'] with tag CASE3_Recovery - FAIL (error)
    • IP connectivity failed
  • 3.39 Check number of topology elements - PASS (tick)
  • 3.40 Stopping Mininet - PASS (tick)
  • 3.41 Copying karaf logs - PASS (tick)
  • No labels