<img src="https://onos-jenkins.onlab.us/job/Pipeline_postjob_BM/lastSuccessfulBuild/artifact/VPLSfailsafe_onos-1.12_20-builds_graph.jpg", alt="VPLSfailsafe", style="width:525px;height:350px;border:0">

commit 45d55e07522a2a4cb0b63a26d02ecfa16de5ecd6 (HEAD, origin/onos-1.12, onos-1.12)
Author: Charles Chan [rascov@gmail.com]
AuthorDate: Thu Nov 30 15:37:50 2017 -0800
Commit: Charles Chan [rascov@gmail.com]
CommitDate: Tue Dec 19 16:25:40 2017 -0800

Dual-homing probing improvements

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

Set up ONOS with 3 node(s) ONOS cluster

• 1.1 Constructing test variables - PASS
• 1.2 Apply cell to environment - PASS
• 1.3 Uninstalling ONOS package - PASS
• 1.4 Creating ONOS package - PASS
• 1.5 Installing ONOS package - PASS
• 1.6 Set up ONOS secure SSH - PASS
• 1.7 Checking ONOS service - PASS
• 1.8 Starting ONOS CLI sessions - PASS
• 1.9 Starting Mininet - PASS
• 1.10 Activate apps defined in the params file - No Result
• 1.11 Set ONOS configurations - No Result
• 1.12 App Ids check - PASS

Case 2: - FAIL

• 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 - FAIL
• Connectivity is not as expected
• 2.8 Loading vpls configuration in case any configuration was missed. - PASS

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

• 50.1 Check intent states - FAIL
• Not all Intents in installed state
• 50.2 Testing connectivity... - FAIL
• Connectivity is NOT as expected.

Case 100: Bring down one host at a time and test connectivity. - 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... - FAIL
• Connectivity failed.
• 100.4 Re-adding link between s1 and h1. - PASS
• 100.5 Discover h1 using ping. - No Result
• 100.6 Check intent states - FAIL
• Not all Intents in installed state
• 100.7 Testing connectivity... - FAIL
• Connectivity is NOT as expected.

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

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