1.11-VPLSfailsafe

commit 8eb1025c98cf3ee33928e4d1fea771ae4399bdf9 (HEAD, origin/onos-1.11, onos-1.11)
Author: Ray Milkey [ray@opennetworking.org]
AuthorDate: Tue Mar 27 13:58:08 2018 -0700
Commit: Ray Milkey [ray@opennetworking.org]
CommitDate: Thu Apr 5 23:37:07 2018 +0000

Fix bug when publishing maintenance release docs
--
(cherry picked from commit 859e04187624c3f01919b37584a98d7e92993884)

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