Page History

...

<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 304b6644a1ac82c8929d1e04dc55ab69fffd65f4 515f5f3b88135f9450b8c53c288f297c10c9d246 (HEAD -] master, origin/master, origin/HEAD)
Author: Carmelo Cascone [carmelo@opennetworking.orgDaniel Park [dan.mcpark84@gmail.com]
AuthorDate: Thu Jan 28 Mon Feb 22 17:2512:16 20 2021 -0800+0900
Commit: Carmelo Cascone Jian Li [carmelo@opennetworkingpyguni@gmail.orgcom]
CommitDate: Fri Wed Feb 5 1824 00:0244:04 00 2021 +0000
Add digest to P4InfoBrowser
Initializes gateway type of kubevirt node.
--
(cherry picked from commit 08be25533d09c3ba8023f4d34e07f4555d6013aa54d8baf7cf1042251067641cf1da99cbc0ae8638)

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 FAIL
• Flow count looks wrong; found 0, expecting at least 116
• 1.19 Check whether all flow status are ADDED - PASS FAIL
• Flow status is wrong!
• 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 FAIL
• Flow count looks wrong; found 0, expecting at least 116
• 1.33 Check whether all flow status are ADDED - PASS FAIL
• Flow status is wrong!
• 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

...

• IP connectivity failed

...

• IP connectivity failed

...

• IP connectivity failed

...

• IP connectivity failed

...

• IP connectivity failed

...

• IP connectivity failed

...

-

...

• IP connectivity failed

...

FAIL

...

• IP connectivity failed

...

• IP connectivity failed

...