Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

HTML

<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 06799d6a3e262c80ad05926d64301afb0db82718 (HEAD, origin/master, origin/HEAD, master)
Author: Yi Tseng Andrea Campanella [yi@opennetworkingandrea@opennetworking.org]
AuthorDate: Fri Mon Sep 1 1613 12:02:56 2017 -070037:36 2021 +0200
Commit: Yi Tseng Andrea Campanella [yi@opennetworkingandrea@opennetworking.org]
CommitDate: Fri Mon Sep 1 1620 07:02:56 2017 -0700
Activate distributed route store while activate DHCP relay app18: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 (tick)
  • 1.2 Apply cell to environment - PASS (tick)
  • 1.3 Uninstalling Atomix - PASS (tick)
  • 1.4 Uninstalling ONOS package - PASS (tick)
  • 1.4 5 Creating ONOS package - PASS (tick)
  • 1.6 Installing Atomix - PASS (tick)
  • 1.7 5 Installing ONOS package - PASS (tick)
  • 1.6 8 Set up ONOS secure SSH - PASS (tick)
  • 1.7 9 Checking ONOS service - PASS (tick)
  • 1.8 10 Starting ONOS CLI sessions - PASS (tick)
  • 1.11 Checking ONOS nodes - PASS (tick)
  • 1.12 Checking ONOS applications - PASS (tick)
  • 1.9 13 Starting Mininet - PASS (tick)
  • 1.10 14 Activate apps defined in the params file - No Result (warning)
  • 1.11 15 Set ONOS configurations - No Result (warning)
  • 1.12 16 App Ids check - PASS (tick)

Case 2: - PASS

...

  • 200.1 Delete s5. - PASS (tick)
  • 200.2 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 200.3 Testing connectivity... - PASS (tick)FAIL (error)
    • Connectivity failed.
  • 200.4 Add s5. - PASS (tick)
  • 200.5 Reconnecting links on s5. - No Result (warning)
  • 200.6 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 200.7 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 200.8 Delete s6. - FAIL (error)
    • Failed to delete switch.
  • 200.9 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 200.10 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 200.11 Add s6. - FAIL (error)
    • Failed to add switch.
  • 200.12 Reconnecting links on s6. - No Result (warning)
  • 200.13 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 200.14 Testing connectivity... - FAIL (error)
    • 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.

...

  • Not all Intents in installed state

...

  • Connectivity failed.

...

Stop

...

  • Connectivity failed.

...

  • Apps are NOT the same across all nodes.

...

  • Not all Intents in installed state

...

  • Connectivity failed.

...

  • Connectivity failed.

...

  • Apps are NOT the same across all nodes.

...

  • Not all Intents in installed state

...

  • Connectivity is NOT as expected.

...

one

...

  • Not all Intents in installed state

...

  • Connectivity failed.

...

ONOS node

...

  • Not all Intents in installed state

...

  • Connectivity failed.

...

  • Connectivity is NOT as expected.

...

at a time and test connectivity. - FAIL