Page History

...

...

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

commit 18fdda8cb850b6e6f22f98180f4e1c35e6267b5e (HEAD -] master commit b0734599424c869860725e421f3aac9fa5a26c45 (HEAD, origin/master, origin/HEAD, master)
Author: Thomas Vachuska Andrea Campanella [tom@opennetworkingandrea@opennetworking.org]
AuthorDate: Tue Jul 18 17:13:01 2017 -0700Mon Sep 13 12:37:36 2021 +0200
Commit: Thomas Vachuska Andrea Campanella [tom@opennetworkingandrea@opennetworking.org]
CommitDate: Tue Jul 18 17:13:01 2017 -0700
Adding utility to provide STC warden status.Mon 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:

...

Setup the test environment including installing ONOS, starting Mininet and ONOScli sessions.

Starting up 3 node(s) ONOS cluster - PASS

Set up ONOS with 3 node(s) ONOS cluster

• 1.1 Constructing test variables - PASS 1.1 Create cell file - No Result
• 1.2 Applying Apply cell variable to environment - No Result PASS
• 1.3 Starting Mininet Uninstalling Atomix - PASS
• 1.4 Uninstalling ONOS package - PASS
• 1.5 Creating ONOS package - PASS
• 1.6 Installing Atomix - PASS
• 1.7 5 Installing ONOS package - PASS
• 1.6 8 Set up ONOS secure SSH - PASS
• 1.7 9 Checking if ONOS is up yet service - PASS
• 1.8 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 9 Activate apps defined in the params file - No Result
• 1.10 15 Set ONOS configurations - No Result
• 1.11 16 App Ids check - PASS

Case 2: - PASS

...

• 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 failed.
• 200.8 Delete s6. - FAIL
• Failed to delete switch.
• 200.9 Check intent states - FAIL
• Not all Intents in installed state
• 200.10 Testing connectivity... - FAIL
• Connectivity failed.
• 200.11 Add s6. - FAIL
• Failed to add switch.
• 200.12 Reconnecting links on s6. - No Result
• 200.13 Check intent states - FAIL
• Not all Intents in installed state
• 200.14 Testing connectivity... - FAIL
• Connectivity is NOT as expected.

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

...

• Connectivity failed.

...

• Apps are NOT the same across all nodes.

...

• Connectivity failed.

...

• Connectivity failed.

...

• Apps are NOT the same across all nodes.

...

• Connectivity failed.

...

Stop

...

• Connectivity failed.

...

• Apps are NOT the same across all nodes.

...

• Not all Intents in installed state

...

• Connectivity is NOT as expected.

...

one ONOS node at a time and test connectivity. - FAIL

...

• Connectivity failed.

...

• Not all Intents in installed state

...

• Connectivity failed.

...

• Not all Intents in installed state

...