Page History

...

<img src="https://jenkins.onosproject.org/view/QA/job/postjob-BM/lastSuccessfulBuild/artifact/VPLSfailsafe_onos-2.2_20-builds_graph.jpg", alt="VPLSfailsafe", style="width:525px;height:350px;border:0">

commit 3144060d46f3a63fd93a4baa9cab00ff2dbd8238 4827b8477d7f3272733bb2d4e8fc917160f87e2f (HEAD -] onos-2.2, origin/onos-2.2)
Author: pierventre Jian Li [pier@opennetworkingpyguni@gmail.orgcom]
AuthorDate: Tue Dec 15 17:34:54 2020 +0100Fri Jan 29 00:01:51 2021 +0900
Commit: pierventre Jian Li [pier@opennetworkingpyguni@gmail.orgcom]
CommitDate: Tue Thu Jan 5 2228 15:2328:25 04 2021 +0100
[AETHER-1032] Backport AETHER-538 to fabric.p40000

Fix: register more missing classes related fabric8 pod into kryo

Case 1: Starting

...

up

...

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 - FAIL
• Net Cfg not added for vpls
• 2.6 Check vpls app configurations - FAIL
• VPLS not configured correctly
• 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. - PASS

• 50.1 Check intent states - PASS
• 50.2 Testing connectivity... - PASS

Case 100: Bring down one host at a time and test connectivity. - FAIL

...

• Not all Intents in installed state

...

• Not all Intents in installed state

...

• Not all Intents in installed state

...

• Not all Intents in installed state

...

- FAIL

...

• Not all Intents in installed state

...

• Not all Intents in installed state

...

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

...