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_master_20-builds_graph.jpg", alt="VPLSfailsafe", style="width:525px;height:350px;border:0"> |
commit 933b0fe7bb8639124a5679714e4d80462953a012 86741ece0495abaff55e34823370b91886df55d1 (HEAD, origin/master, origin/HEAD, master)
Author: Ai Hamano Jordan Halterman [ai.hamano@ntt-at.co.jpjordan@opennetworking.org]
AuthorDate: Fri Nov 30 Mon Dec 10 11:2202:37 31 2018 +0900-0800
Commit: Andrea Campanella Jordan Halterman [andrea@opennetworkingjordan@opennetworking.org]
CommitDate: Tue Wed Dec 4 2312 00:0016:49 07 2018 +0000
[ODTN]Update TAPI YANG files
Ensure master is excluded from backups list when reading role info from mastership service
Case 1: Starting up 3 node(s) ONOS cluster - PASS
...
- 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
- 100.4 Re-adding link between s1 and h1. - PASS
- 100.5 Discover h1 using ping. - No Result
- 100.6 Check intent states - PASS
- 100.7 Testing connectivity... - PASS
- 100.8 Kill link between s2 and h2. - PASS
- 100.9 Check intent states - FAIL
- Not all Intents in installed state
- 100.10 Testing connectivity... - PASS
- 100.11 Re-adding link between s2 and h2. - PASS
- 100.12 Discover h2 using ping. - No Result
- 100.13 Check intent states - PASS
- 100.14 Testing connectivity... - PASS
- 100.15 Kill link between s3 and h3. - PASS
- 100.16 Check intent states - FAIL
- Not all Intents in installed state
- 100.17 Testing connectivity... - PASS
- 100.18 Re-adding link between s3 and h3. - PASS
- 100.19 Discover h3 using ping. - No Result
- 100.20 Check intent states - PASS
- 100.21 Testing connectivity... - PASS
- 100.22 Kill link between s4 and h4. - PASS
- 100.23 Check intent states - FAIL
- Not all Intents in installed state
- 100.24 Testing connectivity... - PASS
- 100.25 Re-adding link between s4 and h4. - PASS
- 100.26 Discover h4 using ping. - No Result
- 100.27 Check intent states - PASS
- 100.28 Testing connectivity... - PASS
- 100.29 Kill link between s5 and h5. - PASS
- 100.30 Check intent states - FAIL
- Not all Intents in installed state
- 100.31 28 Testing connectivity... - PASS
- 100.32 Re-adding link between s5 and h5. - PASS
- 100.33 Discover h5 using ping. - No Result 100. 34 Check intent states - PASS
- 100.35 Testing connectivity... - PASS
- 100.36 Kill link between s6 and h6. - PASS
- 100.37 Check intent states - FAIL
- Not all Intents in installed state
- 100.38 Testing connectivity... - PASS
- 100.39 Re-adding link between s6 and h6. - PASS
- 100.40 Discover h6 using ping. - No Result
- 100.41 Check intent states - PASS 100.42 Testing connectivity... - PASS
- FAIL
- Connectivity is NOT as expected.
Case 200: Bring down one switch at a time and test connectivity. - FAIL
...
- 300.1 Stop ONOS node 0. - PASS
- 300.2 Testing connectivity... - FAIL
- Connectivity failed.
- 300.3 Restart ONOS node 0 and checking status of restart. - PASS
- 300.4 Checking ONOS nodes. - FAIL
- Apps are NOT the same across all nodes.
- 300.5 Check intent states - PASS FAIL
- Not all Intents in installed state
- 300.6 Testing connectivity... - FAIL
- Connectivity is NOT as expected.
...
- 310.1 Killing ONOS node 1. - PASS
- 310.2 Waiting for ONOS to restart. - No Result
- 310.3 Check intent states - PASS FAIL
- Not all Intents in installed state
- 310.4 Testing connectivity... - FAIL
- Connectivity is NOT as expected.
...
- 400.1 Bring down link: s1 to h1 - PASS
- 400.2 Check intent states - PASS FAIL
- Not all Intents in installed state
- 400.3 Testing connectivity... - FAIL
- Connectivity failed.
- 400.4 Adding link: s1 to h1. - PASS
- 400.5 Check intent states - PASS FAIL
- Not all Intents in installed state
- 400.6 Testing connectivity... - FAIL
- Connectivity is NOT as expected.