master-VPLSfailsafe

commit 85d26e7d456f71d0784676e86b2b6381b1b9e06e (HEAD -] master, origin/master, origin/HEAD)
Author: Jian Li [pyguni@gmail.com]
AuthorDate: Fri Apr 16 18:20:22 2021 +0900
Commit: Jian Li [pyguni@gmail.com]
CommitDate: Mon Apr 19 20:12:28 2021 +0900

Bumpup fabric8 kubernetes client to 5.3.0

Case 1: Starting up 3 node(s) ONOS cluster - PASS

Set up ONOS with 3 node(s) ONOS cluster

• 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.5 Creating ONOS package - PASS
• 1.6 Installing Atomix - PASS
• 1.7 Installing ONOS package - PASS
• 1.8 Set up ONOS secure SSH - PASS
• 1.9 Checking ONOS service - PASS
• 1.10 Starting ONOS CLI sessions - PASS
• 1.11 Checking ONOS nodes - PASS
• 1.12 Checking ONOS applications - PASS
• 1.13 Starting Mininet - PASS
• 1.14 Activate apps defined in the params file - No Result
• 1.15 Set ONOS configurations - No Result
• 1.16 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 - 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
• 50.2 Testing connectivity... - 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 - PASS
• 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
• 100.7 Testing connectivity... - FAIL
• Connectivity is NOT as expected.

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

• 200.1 Delete s5. - PASS
• 200.2 Check intent states - PASS
• 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 - PASS
• 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 - PASS
• 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 - PASS
• 310.4 Testing connectivity... - FAIL
• Connectivity is NOT as expected.

Case 400: Bring down one link at a time and test connectivity. - FAIL

• 400.1 Bring down link: s1 to h1 - PASS
• 400.2 Check intent states - PASS
• 400.3 Testing connectivity... - FAIL
• Connectivity failed.
• 400.4 Adding link: s1 to h1. - PASS
• 400.5 Check intent states - PASS
• 400.6 Testing connectivity... - FAIL
• Connectivity is NOT as expected.