Page History

...

<img src="https://jenkins.onosproject.org/view/QA/job/postjob-BM/lastSuccessfulBuild/artifact/VPLSfailsafe_onos-2.0_20-builds_graph.jpg", alt="VPLSfailsafe", style="width:525px;height:350px;border:0">

commit ffeb196152315802e9c4519e4a6e095cec7c26cd 1990278de6f59d84cd81aebe84135050122b056b (HEAD, origin/onos-2.0, onos-2.0)
Author: Ray Milkey Thomas Vachuska [ray@opennetworkingtom@opennetworking.org]
AuthorDate: Fri Feb 8 16:52:25 2019 -0800Mon Apr 15 09:42:24 2019 -0700
Commit: Ray Milkey Thomas Vachuska [ray@opennetworkingtom@opennetworking.org]
CommitDate: Sun Feb 10 03:25:20 2019 +0000
Allow Atomix fetch command to follow redirects
--
(cherry picked from commit 79705aab230752c3f72b58a65c6e1d265c4c3285)Mon Apr 15 09:46:35 2019 -0700

Replaced test mock with existing adapter in archetypes.

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... - PASS
• 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 - FAIL
• Not all Intents in installed state
• 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 - FAIL
• Not all Intents in installed state
• 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.