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 c44ccc7dd03f06d81ddd60791f87aae634cc85ab 63f191f04674423f65ba81af7823047498218115 (HEAD -] master, origin/master, origin/HEAD)
Author: pierventre Jian Li [pier@opennetworkingpyguni@gmail.orgcom]
AuthorDate: Mon Thu Mar 22 2225 17:1714:21 40 2021 +01000900
Commit: Pier Luigi Ventre [pier@opennetworking.orgJian Li [pyguni@gmail.com]
CommitDate: Wed Thu Mar 24 25 15:1735:20 53 2021 +0000
[AETHER-1324] Force push pipeline config
--
(cherry picked from commit ce191fe9983698b3988bee8e6e8c41382ab1fce3)
Obtains the external patch port by referring to gateway bridge name
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 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 Killing ONOS instances with index(es): [0] - PASS
- 1.24 Check number of topology elements - 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 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 0, 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 - PASS
- 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 - PASS
- 1.38 Stopping Mininet - PASS
- 1.39 Copying karaf logs - PASS
...