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.
...
HTML |
---|
<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 8d630f1091c63ff6e7b4ea31669344c5274773cc 1e0f3e8d797e3195ce36950c96c11211f5b98c08 (HEAD -] master, origin/master, origin/HEAD)
Author: Daniele Moro Jian Li [daniele@opennetworkingpyguni@gmail.orgcom]
AuthorDate: Tue Thu Jun 15 2017 11:5306:22 36 2021 +02000900
Commit: Carmelo Cascone Jian Li [carmelo@opennetworkingpyguni@gmail.orgcom]
CommitDate: Wed Fri Jun 16 2218 01:4127:02 2021 +0000
[SDFAB-189] UpfProgrammable implementation for fabric v1model
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'
06 2021 +0000
Not add node into the cluster if it is tainted with kubevirt.io key
--
(cherry picked from commit 552314f8e0c66bc94d2e1070fbb3ca4ac2f841e7)
Case 1
...
: Bridging and Routing Link Failure test with 2x2 leaf-spine topology and
...
1
...
- 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)
...
- Flow count looks wrong; found 6, expecting at least 116
...
- 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 6, expecting at least 116
...
- 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 4 devices (4 expected) and 0 links (8 expected) and 3 controllers (3 expected) and 4 SCCs (1 expected)
...
Onos - FAIL
...