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 137 Next »

SROnosFailure at 26 Aug 2021 22:19:56

SROnosFailure-stratum

commit acf88aeeb8f41556011d10ab2c653d4d0b897b85 (HEAD -] master, origin/master, origin/HEAD)
Author: Jian Li [pyguni@gmail.com]
AuthorDate: Thu Aug 26 22:04:08 2021 +0900
Commit: Jian Li [pyguni@gmail.com]
CommitDate: Thu Aug 26 14:43:34 2021 +0000

Fix: use k8s API config IP address as the controller's IP
--
(cherry picked from commit 90613fc8b563f96866f390f3c47f857c79344972)

Case 1: ONOS Failure test with 2x2 leaf-spine topology - 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 - 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 4 devices (4 expected) and 0 links (8 expected) and 3 controllers (3 expected) and 4 SCCs (1 expected)
  • 1.18 Check whether the flow count is >= 116 - FAIL (error)
    • Flow count looks wrong; found 6, 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 - 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 4 devices (4 expected) and 0 links (8 expected) and 2 controllers (2 expected) and 4 SCCs (1 expected)
  • 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 6, 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 - 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 4 devices (4 expected) and 0 links (8 expected) and 3 controllers (3 expected) and 4 SCCs (1 expected)
  • 1.38 Stopping Mininet - PASS (tick)
  • 1.39 Copying karaf logs - PASS (tick)

Case 2: ONOS Failure test with 4x4 dual-homed leaf-spine topology - 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 Stopping Mininet - PASS (tick)
  • 2.15 Copying karaf logs - PASS (tick)
    • Skipping the rest of this case. 'mininetArgs'

Case 3: ONOS Failure test with single ToR - 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