Page History

...

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

commit 55f451d6170f3d0940d6a816b0e0e3d4066eb307 74b354556ee81ee5896db8fc3fcfd3462a35d722 (HEAD, origin/onos-1.12, onos-1.12)
Author: Charles Chan [rascov@gmail.com]
AuthorDate: Thu Nov 30 13:52:37 2017 -0800Aug 16 21:02:34 2018 -0700
Commit: Ray Milkey Charles Chan [ray@opennetworkingcharles@opennetworking.org]
CommitDate: Thu Nov 30 23:01:45 2017 +0000
Fix CORD-2326 Dual home host loses one of its location when its name being changed in GUIFri Aug 17 17:44:35 2018 +0000

Do not queue VERIFY objectives

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 Checking ONOS nodes - PASS
• 1.10 Checking ONOS applications - PASS
• 1.11 Starting Mininet - PASS
• 1.10 12 Activate apps defined in the params file - No Result
• 1.11 13 Set ONOS configurations - No Result
• 1.12 14 App Ids check - PASS

Case 2: - 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 - FAIL
• Not all Intents in installed state
• 200.7 Testing connectivity... - FAIL
• Connectivity is NOT as expected.

...

at a time and test

...

connectivity

...

. - FAIL

...

• Connectivity failed.

...

• Apps are NOT the same across all nodes.

...

• Not all Intents in installed state

...

• 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

...

• Not all Intents in installed state

...

• Connectivity failed.

...

• Not all Intents in installed state

...