Page History

...

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

commit 2b4de873e4033b7973b399d25cb8828a73bc2e24 581c8407e613a27aaa573a600828b30a37066fb8 (HEAD -] master, origin/master, origin/HEAD)
Author: Thomas Vachuska pierventre [tom@opennetworkingpier@opennetworking.org]
AuthorDate: Tue Mar 30 16:31:34 2021 -0700Thu Sep 23 19:03:14 2021 +0200
Commit: Charles Chan [charles@opennetworkingPier Luigi Ventre [pier@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: Bridging and Routing Link Failure test with 2x2 Leaf-spine and 1 Onos - 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 - FAIL
• Flow count looks wrong; found 0, expecting at least 116
• 1.19 Check whether all flow status are ADDED - 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 Kill link between spine101 and leaf2 - PASS
• 1.24 Checking topology after link down - 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 Restore link between spine101 and leaf2 - PASS
• 1.29 Check whether the flow count is >= 116 - FAIL
• Flow count looks wrong; found 0, expecting at least 116
• 1.30 Check whether all flow status are ADDED - FAIL
• Flow status is wrong!
• 1.31 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE1_Recovery - PASS
• 1.32 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE1_Recovery - FAIL
• IP connectivity failed
• 1.33 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE1_Recovery - FAIL
• IP connectivity failed
• 1.34 Check number of topology elements - PASS
• 1.35 Stopping Mininet - PASS
• 1.36 Copying karaf logs - PASS

Case 2: Bridging and Routing Link Failure test with 4x4 Leaf-spine and 1 Onos - 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 24 links (32 expected) and 1 controllers (1 expected) and 3 SCCs (1 expected)
• 2.17 Check whether the flow count is >= 350 - FAIL
• Flow count looks wrong; found 0, expecting at least 350
• 2.18 Check whether all flow status are ADDED - FAIL
• 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 - PASS
• 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 Kill link between spine101 and leaf2 - PASS
• 2.23 Checking topology after link down - FAIL
• Topology after link down is incorrect
• 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 Restore link between spine101 and leaf2 - FAIL
• Failed to bring link up
• 2.28 Check whether the flow count is >= 350 - FAIL
• Flow count looks wrong; found 0, expecting at least 350
• 2.29 Check whether all flow status are ADDED - FAIL
• Flow status is wrong!
• 2.30 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4', u'h5', u'h6', u'h7', u'h8'] with tag CASE2_Recovery - PASS
• 2.31 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE2_Recovery - FAIL
• IP connectivity failed
• 2.32 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE2_Recovery - FAIL
• IP connectivity failed
• 2.33 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 24 links (32 expected) and 1 controllers (1 expected) and 3 SCCs (1 expected)
• 2.34 Stopping Mininet - PASS
• 2.35 Copying karaf logs - PASS

Mon Sep 27 19:27:55 2021 +0000

[SDFAB-616] Inconsistent format of port number in DhcpRelay
--
(cherry picked from commit 61bd673eec2282aff175daff141059870db78c7d)

Case 1

...

: Bridging and Routing Link Failure test with 2x2

...

leaf-spine topology and

...

1

...

• Flow count looks wrong; found 0, expecting at least 116

...

• Flow status is wrong!

...

• IP connectivity failed

...

• IP connectivity failed

...

• IP connectivity failed

...

• IP connectivity failed

...

• Flow count looks wrong; found 0, expecting at least 116

...

• Flow status is wrong!

...

• IP connectivity failed

...

• IP connectivity failed

...

Onos - 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)

...

• Flow count looks wrong; found 0, expecting at least 350

...

• Flow status is wrong!

...

• IP connectivity failed

...

• IP connectivity failed

...

• IP connectivity failed

...

• Topology after link down is incorrect

...

• IP connectivity failed

...

• IP connectivity failed

...

• IP connectivity failed

...

• Failed to bring link up

...

• Flow count looks wrong; found 0, expecting at least 350

...

• Flow status is wrong!

...

• IP connectivity failed

...

• IP connectivity failed

...

• IP connectivity failed

...

• 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)

...