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 e0eaf5c7bfaacca5f03a188bc9d33df532b768fa 581c8407e613a27aaa573a600828b30a37066fb8 (HEAD -] master, origin/master, origin/HEAD)
Author: Jian Li pierventre [pyguni@gmailpier@opennetworking.comorg]
AuthorDate: Mon Thu Sep 6 1023 19:0203:13 14 2021 +09000200
Commit: Jian Li [pyguni@gmail.comPier Luigi Ventre [pier@opennetworking.org]
CommitDate: Mon Sep 6 0827 19:2827:48 55 2021 +0000
Check node init status when probing node health through REST API
[SDFAB-616] Inconsistent format of port number in DhcpRelay
--
(cherry picked from commit 6a08072a2c1c3094818268ebf22ffa82f971312561bd673eec2282aff175daff141059870db78c7d)
Case 1: Bridging and Routing Link Failure test with 2x2 leaf-spine topology and 1 Onos - FAIL
...
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 1 controllers (1 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 1 controllers (1 expected) and 4 SCCs (1 expected)
...
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'
...
: 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
...