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/SROnosFailure-stratum_master_20-builds_graph.jpg", alt="SROnosFailure-stratum", style="width:525px;height:350px;border:0"> |
commit 066b09da1c4caab771995df05fec62e13ec7fa09 (HEAD -] master, origin/master, origin/HEAD)
Author: Eesha Deepak [eesha@opennetworking.org]
AuthorDate: Tue Jul 20 08:15:47 2021 -0700
Commit: Carmelo Cascone [carmelo@opennetworking.org]
CommitDate: Mon Jul 26 22:42:24 2021 +0000
added the gnmi drivers to the publish target list
Case 1: ONOS Failure test with 2x2 leaf-spine topology - 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 3 controllers (3 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 Killing ONOS instances with index(es): [0] - PASS
- 1.24 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 2 controllers (2 expected) and 4 SCCs (1 expected)
- 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 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 - FAIL
- Flow count looks wrong; found 6, expecting at least 116
- 1.33 Check whether all flow status are ADDED - FAIL
- Flow status is wrong!
- 1.34 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE1_Recovery - FAIL
- IP connectivity failed
- 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 - 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)
- 1.38 Stopping Mininet - PASS
- 1.39 Copying karaf logs - PASS
Case 2: ONOS Failure test with 4x4 dual-homed leaf-spine topology - 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 3: ONOS Failure test with single ToR - FAIL
...
- Flow count looks wrong; found 0, expecting at least 15
...
- Flow status is wrong!
...
- IP connectivity failed
...
- IP connectivity failed
...
- IP connectivity failed
...
- IP connectivity failed
...
- IP connectivity failed
...
- IP connectivity failed
...
- Flow count looks wrong; found 0, expecting at least 15
...
- Flow status is wrong!
...
- IP connectivity failed
...
- IP connectivity failed
...
- IP connectivity failed
...