Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
SROnosFailure at 02 Feb 2021 21:48:00
commit e98dead599045c3f51d650afdac07d305418c8b6 (HEAD -] master, origin/master, origin/HEAD)
Author: Carmelo Cascone [carmelo@opennetworking.org]
AuthorDate: Thu Jan 28 18:25:59 2021 -0800
Commit: pierventre [pier@opennetworking.org]
CommitDate: Tue Feb 2 08:41:08 2021 +0100
Fix issues seen during bundle refresh with shared executors
Case 1: ONOS Failure test with 2x2 Leaf-spine - FAIL
- 1.1 Constructing test variables - PASS
- 1.2 Apply cell to environment - PASS
- 1.3 Uninstalling Atomix - PASS
- 1.4 Uninstalling ONOS package - PASS
- 1.5 Building ONOS Docker image - PASS
- 1.6 Create Cluster Config - PASS
- 1.7 Installing Atomix via docker containers - PASS
- 1.8 Installing ONOS via docker containers - PASS
- 1.9 Set up ONOS secure SSH - PASS
- 1.10 Starting ONOS CLI sessions - PASS
- 1.11 Checking ONOS nodes - PASS
- 1.12 Checking ONOS applications - PASS
- 1.13 Set logging levels - PASS
- 1.14 Set ONOS configurations - PASS
- 1.15 Starting Mininet Topology - PASS
- 1.16 Configure switches in ONOS - PASS
- 1.17 Check number of topology elements - PASS
- 1.18 Check whether the flow count is >= 116 - PASS
- 1.19 Check whether all flow status are ADDED - PASS
- 1.20 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE1 - PASS
- 1.21 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE1 - FAIL
- IP connectivity failed
- 1.22 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE1 - FAIL
- IP connectivity failed
- 1.23 Killing ONOS instances with index(es): [0] - PASS
- 1.24 Check number of topology elements - PASS
- 1.25 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE1_Failure - PASS
- 1.26 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE1_Failure - FAIL
- IP connectivity failed
- 1.27 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE1_Failure - FAIL
- IP connectivity failed
- 1.28 Recovering ONOS instances with index(es): [0] - PASS
- 1.29 Checking if ONOS CLI is ready - PASS
- 1.30 Checking ONOS nodes - PASS
- 1.31 Check number of topology elements - PASS
- 1.32 Check whether the flow count is >= 116 - PASS
- 1.33 Check whether all flow status are ADDED - PASS
- 1.34 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE1_Recovery - PASS
- 1.35 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE1_Recovery - FAIL
- IP connectivity failed
- 1.36 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE1_Recovery - FAIL
- IP connectivity failed
- 1.37 Check number of topology elements - PASS
- 1.38 Stopping Mininet - PASS
- 1.39 Copying karaf logs - PASS
Case 2: ONOS Failure test with 4x4 Leaf-spine - FAIL
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling Atomix - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.4 Building ONOS Docker image - PASS
- 2.5 Create Cluster Config - PASS
- 2.6 Installing Atomix via docker containers - PASS
- 2.7 Installing ONOS via docker containers - PASS
- 2.8 Set up ONOS secure SSH - PASS
- 2.9 Starting ONOS CLI sessions - PASS
- 2.10 Checking ONOS nodes - PASS
- 2.11 Checking ONOS applications - PASS
- 2.12 Set logging levels - PASS
- 2.13 Set ONOS configurations - PASS
- 2.14 Starting Mininet Topology - PASS
- 2.15 Configure switches in ONOS - PASS
- 2.16 Check number of topology elements - FAIL
- 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 - PASS
- 2.18 Check whether all flow status are ADDED - PASS
- 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
- IP connectivity failed
- 2.20 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE2 - FAIL
- IP connectivity failed
- 2.21 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE2 - FAIL
- IP connectivity failed
- 2.22 Killing ONOS instances with index(es): [0] - PASS
- 2.23 Check number of topology elements - FAIL
- 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
- IP connectivity failed
- 2.25 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE2_Failure - FAIL
- IP connectivity failed
- 2.26 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE2_Failure - FAIL
- IP connectivity failed
- 2.27 Recovering ONOS instances with index(es): [0] - PASS
- 2.28 Checking if ONOS CLI is ready - PASS
- 2.29 Checking ONOS nodes - PASS
- 2.30 Check number of topology elements - PASS
- 2.31 Check whether the flow count is >= 350 - PASS
- 2.32 Check whether all flow status are ADDED - PASS
- 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
- IP connectivity failed
- 2.34 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE2_Recovery - FAIL
- IP connectivity failed
- 2.35 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE2_Recovery - FAIL
- IP connectivity failed
- 2.36 Check number of topology elements - FAIL
- 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
- 2.38 Copying karaf logs - PASS
Case 3: ONOS Failure test with single switch - FAIL
- 3.1 Apply cell to environment - PASS
- 3.2 Uninstalling Atomix - PASS
- 3.3 Uninstalling ONOS package - PASS
- 3.4 Building ONOS Docker image - PASS
- 3.5 Create Cluster Config - PASS
- 3.6 Installing Atomix via docker containers - PASS
- 3.7 Installing ONOS via docker containers - PASS
- 3.8 Set up ONOS secure SSH - PASS
- 3.9 Starting ONOS CLI sessions - PASS
- 3.10 Checking ONOS nodes - PASS
- 3.11 Checking ONOS applications - PASS
- 3.12 Set logging levels - PASS
- 3.13 Set ONOS configurations - PASS
- 3.14 Starting Mininet Topology - PASS
- 3.15 Configure switches in ONOS - PASS
- 3.16 Check number of topology elements - PASS
- 3.17 Check whether the flow count is >= 15 - PASS
- 3.18 Check whether all flow status are ADDED - PASS
- 3.19 Verify full connectivity for [u'h1', u'h2'] with tag CASE3 - PASS
- 3.20 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE3 - FAIL
- IP connectivity failed
- 3.21 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE3 - FAIL
- IP connectivity failed
- 3.22 Verify full connectivity for [u'olt1', u'vsg1'] with tag CASE3 - FAIL
- IP connectivity failed
- 3.23 Killing ONOS instances with index(es): [0] - PASS
- 3.24 Check number of topology elements - PASS
- 3.25 Verify full connectivity for [u'h1', u'h2'] with tag CASE3_Failure - PASS
- 3.26 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE3_Failure - FAIL
- IP connectivity failed
- 3.27 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE3_Failure - FAIL
- IP connectivity failed
- 3.28 Verify full connectivity for [u'olt1', u'vsg1'] with tag CASE3_Failure - FAIL
- IP connectivity failed
- 3.29 Recovering ONOS instances with index(es): [0] - PASS
- 3.30 Checking if ONOS CLI is ready - PASS
- 3.31 Checking ONOS nodes - PASS
- 3.32 Check number of topology elements - PASS
- 3.33 Check whether the flow count is >= 15 - PASS
- 3.34 Check whether all flow status are ADDED - PASS
- 3.35 Verify full connectivity for [u'h1', u'h2'] with tag CASE3_Recovery - PASS
- 3.36 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE3_Recovery - FAIL
- IP connectivity failed
- 3.37 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE3_Recovery - FAIL
- IP connectivity failed
- 3.38 Verify full connectivity for [u'olt1', u'vsg1'] with tag CASE3_Recovery - FAIL
- IP connectivity failed
- 3.39 Check number of topology elements - PASS
- 3.40 Stopping Mininet - PASS
- 3.41 Copying karaf logs - PASS