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 908cff4847cf48a62fdf7bb57d776ef165db29bc 0ae31468d339df9a8981962185573e166dc0df06 (HEAD, origin/master, origin/HEAD, master)
Author: Thomas Vachuska [tom@opennetworking.org柯志勇10068695 [ke.zhiyong@zte.com.cn]
AuthorDate: Tue Oct 16 0823 11:2750:29 40 2018 -0700+0800
Commit: Thomas Vachuska Andrea Campanella [tom@opennetworkingandrea@opennetworking.org]
CommitDate: Tue Wed Oct 16 0824 09:2755:29 48 2018 -0700
Fixing README.md file for github+0000
MeterRequest may be null, if meterRequest is null, the implementation of meterService.withdraw(meterRequest, tmpMeter.id()) will cause an exception.
Case 1: Starting up 3 node(s) ONOS cluster - PASS
...
Case 200: Bring down one switch at a time and test connectivity. - FAIL
- 200.1 Delete s5. - PASS
- 200.2 Check intent states - FAIL
- Not all Intents in installed state
- 200.3 Testing connectivity... - FAIL
- Connectivity failed.
- 200.4 Add s5. - PASS
- 200.5 Reconnecting links on s5. - No Result
- 200.6 Check intent states - PASS
- 200.7 Testing connectivity... - FAIL
- Connectivity is NOT as expected.
Case 300: Stop one ONOS node 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
- 300.6 Testing connectivity... - FAIL
- Connectivity is NOT as expected.
Case 310: Kill one ONOS node at a time and test connectivity. - FAIL
- 310.1 Killing ONOS node 1. - PASS
- 310.2 Waiting for ONOS to restart. - No Result
- 310.3 Check intent states - PASS
- 310.4 Testing connectivity... - FAIL
- Connectivity is NOT as expected.
Case 400: Bring down one link at a time and test connectivity. - FAIL
- 400.1 Bring down link: s1 to h1 - PASS
- 400.2 Check intent states - 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 - FAIL
- Not all Intents in installed state
- 400.6 Testing connectivity... - FAIL
- Connectivity is NOT as expected.