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 46c54e343da96e2087ceaeb029567c603b2d8801 18fdda8cb850b6e6f22f98180f4e1c35e6267b5e (HEAD -] master, origin/master, origin/HEAD)
Author: nosignal [howard_hsu@edge-core.comAndrea Campanella [andrea@opennetworking.org]
AuthorDate: Mon Apr 20 15:29:32 2020 +0800Sep 13 12:37:36 2021 +0200
Commit: Carmelo Cascone Andrea Campanella [carmelo@opennetworkingandrea@opennetworking.org]
CommitDate: Tue Apr 28 02:44:35 2020 +0000
Fix deps link of perfmarkMon Sep 20 07:18:54 2021 +0000
[VOL-4343] Processing status of ports in order with mastership and connection/disconnection to avoid inconsisten state
--
(cherry picked from commit b0b93ac609e7860d5fd15703a50a0180fbf7a176)
(cherry picked from commit 727ed68ed3edc4512e353af814abe327ee25f143)
Case 1: Starting up 3 node(s) ONOS cluster - PASS
...
- 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 - FAIL
- Not all Intents in installed state
- 200.7 Testing connectivity... - FAIL
- Connectivity is NOT as expected.
Case 300: Stop one ONOS node at a time and test connectivity. - FAIL
...
Stop
...
- Connectivity failed.
...
- Apps are NOT the same across all nodes.
...
- Connectivity is NOT as expected.
...
one ONOS node
...
- 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.
...
at a time and test
...
- Connectivity failed.
...
connectivity
...
. - FAIL
...