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-BM/lastSuccessfulBuild/artifact/VPLSfailsafe_onos-1.12_20-builds_graph.jpg", alt="VPLSfailsafe", style="width:525px;height:350px;border:0"> |
commit 9efb9864744fc71497bae45fc53f4784a6601745 3eaa6e5702264dc0d49b0fab16d4d1ea255b3902 (HEAD, origin/onos-1.12, onos-1.12)
Author: Andrea Campanella Charles Chan [andrea@opennetworkingrascov@gmail.orgcom]
AuthorDate: Tue Fri Mar 20 1630 12:3711:29 34 2018 -0700
Commit: Andrea Campanella Charles Chan [andrea@opennetworkingcharles@opennetworking.org]
CommitDate: Fri Mar 30 23 20:5439:57 30 2018 +0000
Moving Multicast subsystem into app and refactoring APIs to support multihomed sources and sinks
Better error handling
Case 1: Starting up 3 node(s) ONOS cluster - PASS
...
- 1.1 Constructing test variables - PASS
- 1.2 Apply cell to environment - PASS
- 1.3 Uninstalling ONOS package - PASS
- 1.4 Creating ONOS package - PASS
- 1.5 Installing ONOS package - PASS
- 1.6 Set up ONOS secure SSH - PASS
- 1.7 Checking ONOS service - PASS
- 1.8 Starting ONOS CLI sessions - PASS
- 1.9 Starting Mininet - PASS
- 1.10 Activate apps defined in the params file - No Result
- 1.11 Set ONOS configurations - No Result
- 1.12 App Ids check - PASS
Case 2: -
...
FAIL
- 2.1 Discover hosts using pings - No Result
- 2.2 Load VPLS configurations - PASS
- 2.3 Check VPLS configurations - PASS
- 2.4 Check interface configurations - PASS
- 2.5 Check network configurations for vpls application - PASS
- 2.6 Check vpls app configurations - PASS
- 2.7 Check connectivity - PASS FAIL
- Connectivity is not as expected
- 2.8 Loading vpls configuration in case any configuration was missed. - PASS
Case 50: Check connectivity before running all other tests. -
...
FAIL
- 50.1 Check intent states - PASS FAIL
- Not all Intents in installed state
- 50.2 Testing connectivity... - PASS FAIL
- Connectivity is NOT as expected.
Case 100: Bring down one host at a time and test connectivity. - FAIL
...
- 100.1 Kill link between s1 and h1. - PASS
- 100.2 Check intent states - FAIL
- Not all Intents in installed state
- 100.3 Testing connectivity... - PASS FAIL
- Connectivity failed.
- 100.4 Re-adding link between s1 and h1. - PASS
- 100.5 Discover h1 using ping. - No Result
- 100.6 Check intent states - FAIL
- Not all Intents in installed state
- 100.7 Testing connectivity... - FAIL
- Connectivity is NOT as expected.
...