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 393339f16268c241d88df0f8418ac45a6d1c52f9 1733d7e7fdacbd80d92ad1fb871d080393ea5988 (HEAD, origin/onos-1.12, onos-1.12)
Author: Charles Chan [rascov@gmail.comTerje Mikal Mjelde [terje-mikal.mjelde@ffi.no]
AuthorDate: Thu Jan 11 11:48:18 2018 -0800Fri Mar 9 08:31:14 2018 +0100
Commit: Charles Chan Ray Milkey [charles@opennetworkingray@opennetworking.org]
CommitDate: Fri Jan 12 00:02:51 Mar 9 18:54:57 2018 +0000
Resume the use of ICMP type/code in OFDPA driver
[ONOS-7514] Fix for broken EAP introduced in commit f0c4761.

Change-Id: I439bcde21333472e04836acf377890a9ad772683

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

...

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

...

• Not all Intents in installed state

...

• Connectivity failed.

...

• Not all Intents in installed state

...