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 633f794277d4085b502520899ea29a619bd4a8fb commit 3479fd49c732cf3b96c82c45251419ebfeaddc44 (HEAD, origin/master, origin/HEAD, masteronos-1.12, onos-1.12)
Author: Shashikanth VH Andrea Campanella [shashikanthandrea@opennetworking.vh@huawei.comorg]
AuthorDate: Wed Thu Nov 15 1123 16:4538:09 24 2017 +05300100
Commit: Satishk-Huawei [satishk@huawei.comAndrea Campanella [andrea@opennetworking.org]
CommitDate: Wed Tue Nov 15 1328 22:2741:34 48 2017 +0000
Fixed bgp capability processing issue

[ONOS-7527] FIX for OfControllerImpl does not filter by device scheme in DeviceListener
--
(cherry picked from commit 86e0c564d3001bffe84ac4c3ef861b128b2b9477)

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.

...

• 200.1 Delete s5. - PASS
• 200.2 Check intent states - FAIL
• Not all Intents in installed state
• 200.3 Testing connectivity... - PASS 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.

...

• 310.1 Killing ONOS node 1. - PASS
• 310.2 Waiting for ONOS to restart. - No Result
• 310.3 Check intent states - PASS FAIL
• Not all Intents in installed state
• 310.4 Testing connectivity... - FAIL
• Connectivity is NOT as expected.

...