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 cca2eae5ebfd42b9cd22c5802ffc50d974f7fec7 74b354556ee81ee5896db8fc3fcfd3462a35d722 (HEAD, origin/onos-1.12, onos-1.12)
Author: Jordan Halterman Charles Chan [jordan@opennetworkingrascov@gmail.orgcom]
AuthorDate: Wed Dec 20 11:52:46 2017 -0800Thu Aug 16 21:02:34 2018 -0700
Commit: Ray Milkey Charles Chan [ray@opennetworkingcharles@opennetworking.org]
CommitDate: Thu Dec 21 11:34:18 2017 -0800
Increase default primitive operation timeout to 15 secondsFri 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

...

• 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... - FAIL
Connectivity failed.
• PASS
• 100.32 Re-adding link between s5 and h5. - PASS
• 100.33 Discover h5 using ping. - No Result
• 100.34 Check intent states - FAIL
Not all Intents in installed state
• PASS
• 100.35 Testing connectivity... - FAIL
• Connectivity is NOT as expected.

Case 200: Bring down one switch at a time and test connectivity. - FAIL

• PASS
• 100.36 Kill link between s6 and h6. 200.1 Delete s5. - PASS
• 200 100.2 37 Check intent states - FAIL
• Not all Intents in installed state
• 200 100.3 38 Testing connectivity... - PASS 200.4 Add s5
• 100.39 Re-adding link between s6 and h6. - PASS
• 200.5 Reconnecting links on s5 100.40 Discover h6 using ping. - No Result
• 200 100.6 41 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 100.2 42 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 200: Bring down one

...

switch at a time and test connectivity. - FAIL

...

• Not all Intents in installed state

...

• Connectivity failed.

...

• Not all Intents in installed state

...