Page History

...

<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 73a6cc193e30c7669d7fe85b81922a2712bce1bc 45d55e07522a2a4cb0b63a26d02ecfa16de5ecd6 (HEAD, origin/onos-1.12, onos-1.12)
Author: Saurav Das Charles Chan [sauravdas@alumnirascov@gmail.stanford.educom]
AuthorDate: Tue Dec 5 Thu Nov 30 15:0037:23 50 2017 -0800
Commit: Charles Chan [rascov@gmail.com]
CommitDate: Tue Dec 5 1819 16:3525:01 40 2017 -0800
Fix for empty flooding groups due to bucket add/remove commands being reordered, and
Dual-homing probing improvements

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

...

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