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-1.12/1013/

...

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

commit 38d2ff68416e26259304f8654668196dd615408b 9efb9864744fc71497bae45fc53f4784a6601745 (HEAD, origin/onos-1.12, onos-1.12)
Author: ONOS Jenkins User [jenkins@onlab.usAndrea Campanella [andrea@opennetworking.org]
AuthorDate: Fri Tue Mar 20 16 04:0637:34 29 2018 +0000-0700
Commit: ONOS Jenkins User [jenkins@onlab.usAndrea Campanella [andrea@opennetworking.org]
CommitDate: Fri Mar 16 0423 20:0654:34 57 2018 +0000
Starting snapshot 1.12.1-SNAPSHOT
Moving Multicast subsystem into app and refactoring APIs to support multihomed sources and sinks

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

...

  • 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)
  • 7 Testing connectivity... - FAIL (error)
    • Connectivity is NOT as expected.

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