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-Fabric2/lastSuccessfulBuild/artifact/SROnosFailure_onos-2.5_20-builds_graph.jpg", alt="SROnosFailure", style="width:525px;height:350px;border:0"> |
commit 6a7cb471d32a6c237addf5ef0680c62c2614dcd4 78b4d6f3c3060bba748e7b51af615abf796e1e94 (HEAD -] onos-2.5, origin/onos-2.5)
Author: Daniele Moro pierventre [daniele@opennetworkingpier@opennetworking.org]
AuthorDate: Tue Jul 20 15:18:32 Fri Aug 27 17:20:00 2021 +0200
Commit: Daniele Moro [daniele@opennetworkingPier Luigi Ventre [pier@opennetworking.org]
CommitDate: Tue Jul 20 15:18:32 2021 +0200Thu Sep 2 16:29:24 2021 +0000
[SDFAB-287] Let send packet out throw UpfProgrammableException522] Fix port type for pair ports
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 Creating ONOS package - PASS
- 1.6 Installing Atomix - PASS
- 1.7 Installing ONOS package - PASS
- 1.8 Set up ONOS secure SSH - PASS
- 1.9 Checking ONOS service - 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 Check whether the flow count is bigger than 116 - FAIL
- Flow count looks wrong; found False, expecting at least 116
- 1.17 Check whether all flow status are ADDED - FAIL
- Flow status is wrong!
- 1.18 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE1 - FAIL
- IP connectivity failed
- 1.19 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE1 - FAIL
- IP connectivity failed
- 1.20 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE1 - FAIL
- IP connectivity failed
Case 1: ONOS Failure test with 2x2 Leaf-spine - FAIL
Case 1: ONOS Failure test with 2x2 Leaf-spine - FAIL
...
- 1.21 Killing ONOS instances with index(es): [0] - PASS
- 1.22 Check number of topology elements - FAIL
- Unexpected number of links, switches, and/or controllers
- 1.23 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE1_Failure - FAIL
- IP connectivity failed
- 1.24 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE1_Failure - FAIL
- IP connectivity failed
- 1.25 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE1_Failure - FAIL
- IP connectivity failed
- 1.26 Recovering ONOS instances with index(es): [0] - PASS
- 1.27 Checking if ONOS CLI is ready - PASS
- 1.28 Checking ONOS nodes - PASS
- 1.29 Check number of topology elements - PASS
- 1.30 Check whether the flow count is bigger than 116 - PASS
- 1.31 Check whether all flow status are ADDED - PASS
- 1.32 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE1_Recovery - FAIL
- IP connectivity failed
- 1.33 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE1_Recovery - FAIL
- IP connectivity failed
- 1.34 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE1_Recovery - FAIL
- IP connectivity failed
- 1.35 Stopping Mininet - PASS
- 1.36 Copying karaf logs - PASS