Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published from Jenkins build: https://jenkins.onosproject.org/job/USECASE-pipeline-master/1147/

...

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 812460da2788cb8b6dc72057a7ee71047af96cee d33d3b48380a73fe93cc02eb699cbc24cbf77c28 (HEAD, origin/master, origin/HEAD, master)
Author: Jian Li Carmelo Cascone [pyguni@gmailcarmelo@opennetworking.comorg]
AuthorDate: Mon May 13 15:41:30 2019 +0900Tue Jun 18 12:12:36 2019 -0700
Commit: Jian Li Ray Milkey [pyguni@gmailray@opennetworking.comorg]
CommitDate: Mon May 13 07:53:36 Tue Jun 18 22:26:33 2019 +0000
Support to query active status of the nodes through REST API
Build ONOS exclusively with Bazel-provided remote JDK

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

...

Set up ONOS with 3 node(s) ONOS cluster

  • 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.5 Creating ONOS package - PASS (tick)
  • 1.6 Installing Atomix - PASS (tick)
  • 1.7 Installing ONOS package - PASS (tick)
  • 1.8 Set up ONOS secure SSH - PASS (tick)
  • 1.9 Checking ONOS service - PASS (tick)
  • 1.10 Starting ONOS CLI sessions - PASS (tick)
  • 1.11 Checking ONOS nodes - PASS (tick)
  • 1.12 Checking ONOS applications - PASS (tick)
  • 1.13 Starting Mininet - PASS (tick)
  • 1.14 Activate apps defined in the params file - No Result (warning)
  • 1.15 Set ONOS configurations - No Result (warning)
  • 1.16 App Ids check - PASS (tick)

Case 2: - PASS

  • 2.1 Discover hosts using pings - No Result (warning)
  • 2.2 Load VPLS configurations - PASS (tick)
  • 2.3 Check VPLS configurations - PASS (tick)
  • 2.4 Check interface configurations - PASS (tick)
  • 2.5 Check network configurations for vpls application - PASS (tick)
  • 2.6 Check vpls app configurations - PASS (tick)
  • 2.7 Check connectivity - PASS (tick)
  • 2.8 Loading vpls configuration in case any configuration was missed. - PASS (tick)

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

  • 50.1 Check intent states - PASS (tick)
  • 50.2 Testing connectivity... - PASS (tick)

...

FAIL

  • 100.1 Kill link between s1 and h1. - PASS (tick)
  • 100.2 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 100.3 Testing connectivity... - PASS (tick)
  • 100.4 Re-adding link between s1 and h1. - PASS (tick)
  • 100.5 Discover h1 using ping. - No Result (warning)
  • 100.6 Check intent states - PASS (tick)
  • 100.7 Testing connectivity... - PASS (tick)
  • 100.8 Kill link between s2 and h2. - PASS (tick)
  • 100.9 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 100.10 Testing connectivity... - PASS (tick)
  • 100.11 Re-adding link between s2 and h2. - PASS (tick)
  • 100.12 Discover h2 using ping. - No Result (warning)
  • 100.13 Check intent states - PASS (tick)
  • 100.14 Testing connectivity... - PASS (tick)
  • 100.15 Kill link between s3 and h3. - PASS (tick)
  • 100.16 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 100.17 Testing connectivity... - PASS (tick)
  • 100.18 Re-adding link between s3 and h3. - PASS (tick)
  • 100.19 Discover h3 using ping. - No Result (warning)
  • 100.20 Check intent states - PASS (tick)
  • 100.21 Testing connectivity... - PASS (tick)
  • 100.22 Kill link between s4 and h4. - PASS (tick)
  • 100.23 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 100.24 Testing connectivity... - PASS (tick)
  • 100.25 Re-adding link between s4 and h4. - PASS (tick)
  • 100.26 Discover h4 using ping. - No Result (warning)
  • 100.27 Check intent states - PASS (tick)
  • 100.28 Testing connectivity... - PASS (tick)
  • 100.29 Kill link between s5 and h5. - PASS (tick)
  • 100.30 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 100.31 Testing connectivity... - PASS (tick)
  • 100.32 Re-adding link between s5 and h5. - PASS (tick)
  • 100.33 Discover h5 using ping. - No Result (warning)
  • 100.34 Check intent states - PASS (tick)
  • 100.35 Testing connectivity... - PASS (tick)
  • 100.36 Kill link between s6 and h6. - PASS (tick)
  • 100.37 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 100.38 Testing connectivity... - PASS (tick)
  • 100.39 Re-adding link between s6 and h6. - PASS (tick)
  • 100.40 Discover h6 using ping. - No Result (warning)
  • 100.41 Check intent states - PASS (tick)
  • 100.42 Testing connectivity... - PASS (tick)

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

  • 200.1 Delete s5. - PASS (tick)
  • 200.2 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 200.3 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 200.4 Add s5. - PASS (tick)
  • 200.5 Reconnecting links on s5. - No Result (warning)
  • 200.6 Check intent states - PASS (tick)
  • 200.7 Testing connectivity... - FAIL (error)
    • 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 (tick)
  • 300.2 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 300.3 Restart ONOS node 0 and checking status of restart. - PASS (tick)
  • 300.4 Checking ONOS nodes - FAIL (error)
    • Apps are NOT the same across all nodes.
  • 300.5 Check intent states - PASS (tick)
  • 300.6 Testing connectivity... - FAIL (error)
    • 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 (tick)
  • 310.2 Waiting for ONOS to restart. - No Result (warning)
  • 310.3 Check intent states - PASS (tick)
  • 310.4 Testing connectivity... - FAIL (error)
    • 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 (tick)
  • 400.2 Check intent states - PASS (tick)
  • 400.3 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 400.4 Adding link: s1 to h1. - PASS (tick)
  • 400.5 Check intent states - PASS (tick)
  • 400.6 Testing connectivity... - FAIL (error)
    • Connectivity is NOT as expected.