Page History

...

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

commit 132393a4a23dba0706fb6e19fb787561d83d69bc 18fdda8cb850b6e6f22f98180f4e1c35e6267b5e (HEAD -] master, origin/master, origin/HEAD, master)
Author: Charles Chan Andrea Campanella [rascov@gmailandrea@opennetworking.comorg]
AuthorDate: Thu Jan 4 14:26:07 2018 -0800Mon Sep 13 12:37:36 2021 +0200
Commit: Charles Chan Andrea Campanella [rascov@gmailandrea@opennetworking.comorg]
CommitDate: Tue Jan 9 13:55:27 2018 -0800
CORD-2470 Fix NPEsMon Sep 20 07:18:54 2021 +0000

[VOL-4343] Processing status of ports in order with mastership and connection/disconnection to avoid inconsisten state
--
(cherry picked from commit b0b93ac609e7860d5fd15703a50a0180fbf7a176)
(cherry picked from commit 727ed68ed3edc4512e353af814abe327ee25f143)

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 Atomix - PASS
• 1.4 Uninstalling ONOS package - PASS
• 1.4 5 Creating ONOS package - PASS
• 1.6 Installing Atomix - PASS
• 1.5 7 Installing ONOS package - PASS
• 1.6 8 Set up ONOS secure SSH - PASS
• 1.7 9 Checking ONOS service - PASS
• 1.8 10 Starting ONOS CLI sessions - PASS
• 1.11 Checking ONOS nodes - PASS
• 1.12 Checking ONOS applications - PASS
• 1.9 13 Starting Mininet - PASS
• 1.10 14 Activate apps defined in the params file - No Result
• 1.11 15 Set ONOS configurations - No Result
• 1.12 16 App Ids check - PASS

Case 2: -

...

PASS

• 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 - FAIL
• Connectivity is not as expected
• PASS
• 2.8 Loading vpls configuration in case any configuration was missed. - PASS

Case 50: Check connectivity before running all other tests. -

...

PASS

• 50.1 Check intent states - FAIL
Not all Intents in installed state
• PASS
• 50.2 Testing connectivity... - FAIL
Connectivity is NOT as expected.
• PASS

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.
• 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.7 10 Testing connectivity... - PASS
• 100.. - FAIL
• Connectivity is NOT as expected.

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

• 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 200.1 Delete s5. - PASS
• 200 100.2 16 Check intent states - FAIL
• Not all Intents in installed state
• 200 100.3 17 Testing connectivity... - FAIL
• Connectivity failed.
• PASS
• 100.18 Re-adding link between s3 and h3. 200.4 Add s5. - PASS
• 200.5 Reconnecting links on s5 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 200.6 Check intent states - FAIL
• Not all Intents in installed state
• 200 100.7 24 Testing connectivity... - FAIL
• Connectivity is NOT as expected.

Case 300: Stop one ONOS node at a time and test connectivity. - FAIL

• PASS
• 100.25 Re-adding link between s4 and h4. - PASS
• 100.26 Discover h4 using ping. - No Result
• 100.27 Check intent states 300.1 Stop ONOS node 0. - PASS
• 300 100.2 28 Testing connectivity... - FAIL
• Connectivity failed.
• PASS
• 100.29 Kill link between s5 and h5 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 100.30 Check intent states - FAIL
• Not all Intents in installed state
• 300 100.6 31 Testing connectivity... - FAIL
• Connectivity is NOT as expected.

Case 310: Kill one ONOS node at a time and test connectivity. - FAIL

• PASS
• 100.32 Re-adding link between s5 and h5. - PASS
• 100.33 Discover h5 using ping. - No Result
• 100.34 Check intent states - PASS
• 100.35 Testing connectivity.. 310.1 Killing ONOS node 1. - PASS
• 310.2 Waiting for ONOS to restart. - No Result
• 100.36 Kill link between s6 and h6. - PASS
• 100.37 310.3 Check intent states - FAIL
• Not all Intents in installed state
• 310 100.4 38 Testing connectivity... - PASS
• 100.39 Re-adding link between s6 and h6. - PASS
• 100.. - FAIL
• Connectivity is NOT as expected.

...

• 40 Discover h6 using ping. - No Result
• 100.41 Check intent states - PASS
• 100.42 Testing connectivity... - PASS

Case 200: Bring down one

...

switch at a time and test connectivity. - FAIL

• 400 200.1 Bring down link: s1 to h1 Delete s5. - PASS
• 400 200.2 Check intent states - FAIL
• Not all Intents in installed state
• 400 200.3 Testing connectivity... - FAIL
• Connectivity failed.
• 400 200.4 Adding link: s1 to h1Add s5. - PASS
• 400 200.5 Reconnecting links on s5. - No Result
• 200.6 Check intent states - FAIL
• Not all Intents in installed state
• 400 200.6 7 Testing connectivity... - FAIL
• Connectivity is NOT as expected.

Case 300: Stop one ONOS node at a time and test connectivity. - FAIL