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-2.0/1005/

...

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

commit 9092907c9339e02cfb20a4ccd154a75844ce805c 9d3ad8b9d8d8cf9dc6f6c9345757a365b09ff0db (HEAD, origin/onos-2.0, onos-2.0)
Author: ONOS Jenkins User [jenkins@onlab.ushiroki [hiroki.okui@gmail.com]
AuthorDate: Fri Sun Jan 18 20 20:1505:40 51 2019 +0000-0800
Commit: ONOS Jenkins User [jenkins@onlab.usAndrea Campanella [andrea@opennetworking.org]
CommitDate: Fri Jan 18 2025 08:1527:40 17 2019 +0000
Starting snapshot 2.0.1-SNAPSHOT
ONOS-7867 FlowRuleProgrammable driver for OpenConfig Cassini
--
(cherry picked from commit 337c5526d17dff0a1dc5114b015414afc9c221d2)

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)FAIL (error)
    • Not all Intents in installed state
  • 100.42 Testing connectivity... - PASS (tick)FAIL (error)
    • Connectivity is NOT as expected.

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