Page History

...

<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 812460da2788cb8b6dc72057a7ee71047af96cee d33d3b48380a73fe93cc02eb699cbc24cbf77c28 (HEAD, origin/master, origin/HEAD, master)
Author: Jian Li Carmelo Cascone [pyguni@gmailcarmelo@opennetworking.comorg]
AuthorDate: Mon May 13 15:41:30 2019 +0900Tue Jun 18 12:12:36 2019 -0700
Commit: Jian Li Ray Milkey [pyguni@gmailray@opennetworking.comorg]
CommitDate: Mon May 13 07:53:36 Tue Jun 18 22:26:33 2019 +0000
Support to query active status of the nodes through REST API
Build ONOS exclusively with Bazel-provided remote JDK

Case 1: Starting up 3 node(s) ONOS cluster

...

Set up ONOS with 3 node(s) ONOS cluster

...

-

...

Case 2: - PASS

• 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
• 2.8 Loading vpls configuration in case any configuration was missed. - PASS

Case 50: Check connectivity before running all other tests. - PASS

• 50.1 Check intent states - PASS
• 50.2 Testing connectivity... - PASS

...

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
• 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 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

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

...

• Connectivity failed.

...