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 5e8cb53fe79a649152bd378790d3cfc2844fca5b b53d626fb03195129c0ec0802e1f953f85dcbef8 (HEAD -] master, origin/master, origin/HEAD)
Author: pierventre [pier@opennetworking.org]
AuthorDate: Fri Wed Sep 17 2322 11:0224:19 38 2021 +0200
Commit: Pier Luigi Ventre [pier@opennetworking.org]
CommitDate: Wed Thu Sep 22 1623 07:4538:36 2021 +0000

[SDFAB-295] Inconsistent format of port number in host location

...

-612] Cluster not ready when using recent tost master images
--
(cherry picked from commit ec0e942320ef27932b4173172055151015261d7c)

Case 1: Bridging and Routing Link Failure test with 2x2 leaf-spine topology 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 - 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 4 devices (4 expected) and 0 links (8 expected) and 1 controllers (1 expected) and 4 SCCs (1 expected)
• 1.18 Check whether the flow count is >= 116 - FAIL
• Flow count looks wrong; found 6, 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 - FAIL
• IP connectivity failed
• 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 - FAIL
• Topology after link down is incorrect
• 1.25 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE1_Failure - FAIL
• IP connectivity failed
• 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 - FAIL
• Failed to bring link up
• 1.29 Check whether the flow count is >= 116 - FAIL
• Flow count looks wrong; found 6, 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 - FAIL
• IP connectivity failed
• 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 - 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 4 devices (4 expected) and 0 links (8 expected) and 1 controllers (1 expected) and 4 SCCs (1 expected)
• 1.35 Stopping Mininet - PASS
• 1.36 Copying karaf logs - PASS

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

Case 4: Bridging and Routing Link Failure test with 2x2 leaf-spine topology and 3 Onos - FAIL

• 4.1 Apply cell to environment - PASS
• 4.2 Uninstalling Atomix - PASS
• 4.3 Uninstalling ONOS package - PASS
• 4.4 Building ONOS Docker image - PASS
• 4.5 Create Cluster Config - PASS
• 4.6 Installing Atomix via docker containers - PASS
• 4.7 Installing ONOS via docker containers - PASS
• 4.8 Set up ONOS secure SSH - PASS
• 4.9 Starting ONOS CLI sessions - PASS
• 4.10 Checking ONOS nodes - PASS
• 4.11 Checking ONOS applications - PASS
• 4.12 Set logging levels - PASS
• 4.13 Set ONOS configurations - PASS
• 4.14 Starting Mininet Topology - PASS
• 4.15 Configure switches in ONOS - PASS
• 4.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 4 devices (4 expected) and 0 links (8 expected) and 3 controllers (3 expected) and 4 SCCs (1 expected)
• 4.17 Check whether the flow count is >= 116 - FAIL
• Flow count looks wrong; found 6, expecting at least 116
• 4.18 Check whether all flow status are ADDED - FAIL
• Flow status is wrong!
• 4.19 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE3 - FAIL
• IP connectivity failed
• 4.20 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE3 - FAIL
• IP connectivity failed
• 4.21 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE3 - FAIL
• IP connectivity failed
• 4.22 Kill link between spine101 and leaf2 - PASS
• 4.23 Checking topology after link down - FAIL
• Topology after link down is incorrect
• 4.24 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE3_Failure - FAIL
• IP connectivity failed
• 4.25 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE3_Failure - FAIL
• IP connectivity failed
• 4.26 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE3_Failure - FAIL
• IP connectivity failed
• 4.27 Restore link between spine101 and leaf2 - FAIL
• Failed to bring link up
• 4.28 Check whether the flow count is >= 116 - FAIL
• Flow count looks wrong; found 6, expecting at least 116
• 4.29 Check whether all flow status are ADDED - FAIL
• Flow status is wrong!
• 4.30 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE3_Recovery - FAIL
• IP connectivity failed
• 4.31 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE3_Recovery - FAIL
• IP connectivity failed
• 4.32 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE3_Recovery - FAIL
• IP connectivity failed
• 4.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 4 devices (4 expected) and 0 links (8 expected) and 3 controllers (3 expected) and 4 SCCs (1 expected)
• 4.34 Stopping Mininet - PASS
• 4.35 Copying karaf logs - PASS

Case 5: Bridging and Routing Link Failure test with 4x4 dual-homed leaf-spine topology and 3 Onos - FAIL

• 5.1 Apply cell to environment - PASS
• 5.2 Uninstalling Atomix - PASS
• 5.3 Uninstalling ONOS package - PASS
• 5.4 Building ONOS Docker image - PASS
• 5.5 Create Cluster Config - PASS
• 5.6 Installing Atomix via docker containers - PASS
• 5.7 Installing ONOS via docker containers - PASS
• 5.8 Set up ONOS secure SSH - PASS
• 5.9 Starting ONOS CLI sessions - PASS
• 5.10 Checking ONOS nodes - PASS
• 5.11 Checking ONOS applications - PASS
• 5.12 Set logging levels - PASS
• 5.13 Set ONOS configurations - PASS
• 5.14 Stopping Mininet - PASS
• 5.15 Copying karaf logs - PASS
• Skipping the rest of this case. 'mininetArgs'