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/SRClusterRestart_master_20-builds_graph.jpg", alt="SRClusterRestart", style="width:525px;height:350px;border:0"> |
commit 4d29d3c8b67a89ffa3a06dda0efa196ff179d009 cabf6f84272b2b104f8d517f9994c7d845d992dd (HEAD -] master, origin/master, origin/HEAD)
Author: pierventre [pier@opennetworking.orgMatteo Scandolo [matteo.scandolo@gmail.com]
AuthorDate: Fri Aug 27 17:20:00 2021 +0200Thu Sep 16 08:35:43 2021 -0700
Commit: Pier Luigi Ventre [pier@opennetworkingThomas Vachuska [tom@opennetworking.org]
CommitDate: Thu Fri Sep 2 1517 16:0413:32 44 2021 +0000
[SDFAB-522] Fix port type for pair ports
Bumping onos-maven-plugin version in onos-dependencies
Case 1: Cluster Restart 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 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 >= 116 - FAIL
- Flow count looks wrong; found 0, 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
- 1.21 Killing ONOS instances with index(es): [0, 1, 2] - PASS
- 1.22 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE1_Failure - FAIL
- IP connectivity failed
- 1.23 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE1_Failure - FAIL
- IP connectivity failed
- 1.24 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE1_Failure - FAIL
- IP connectivity failed
- 1.25 Recovering ONOS instances with index(es): [0, 1, 2] - PASS
- 1.26 Checking if ONOS CLI is ready - PASS
- 1.27 Checking if ONOS CLI is ready - PASS
- 1.28 Checking if ONOS CLI is ready - PASS
- 1.29 Checking ONOS nodes - PASS
- 1.30 Check number of topology elements - PASS
- 1.31 Check whether the flow count is >= 116 - FAIL
- Flow count looks wrong; found 0, expecting at least 116
- 1.32 Check whether all flow status are ADDED - FAIL
- Flow status is wrong!
- 1.33 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE1_Failure - FAIL
- IP connectivity failed
- 1.34 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE1_Failure - FAIL
- IP connectivity failed
- 1.35 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE1_Failure - FAIL
- IP connectivity failed
- 1.36 Stopping Mininet - PASS
- 1.37 Copying karaf logs - PASS
Case 2: Cluster Restart 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 Creating ONOS package - PASS
- 2.5 Installing Atomix - PASS
- 2.6 Installing ONOS package - PASS
- 2.7 Set up ONOS secure SSH - PASS
- 2.8 Checking ONOS service - 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 - No Result
- 2.14 Stopping Mininet - PASS
- 2.15 Copying karaf logs - PASS
- Skipping the rest of this case. 'mininetArgs'
Case 3: Cluster Restart 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
...
- IP connectivity failed
...
- IP connectivity failed
...
topology
...
- Flow count looks wrong; found 0, expecting at least 15
...
- Flow status is wrong!
...
- IP connectivity failed
...
- IP connectivity failed
...
- IP connectivity failed
...
- FAIL
...
- IP connectivity failed
...