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.1/1003/

...

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

commit 040d6d8c748b6399b74b56abde5894d254eb6383 6ff33a3dc14e0226c7a4bd9c7172f883f6468077 (HEAD , origin/-] onos-2.1, origin/onos-2.1)
Author: Carmelo Cascone [carmelo@opennetworking.orgEsin Karaman [esin.karaman@netsia.com]
AuthorDate: Wed May 8 14:03:01 2019 -0700Tue Mar 5 13:49:02 2019 +0000
Commit: Carmelo Cascone [carmelo@opennetworkingPier Luigi Ventre [pier@opennetworking.org]
CommitDate: Thu May Wed Jun 19 16 21:4234:47 58 2019 +0000
Update P4 programs to compile with most recent p4c
ONOS-7944 McastHandler of SegmentRouting considers only dual-homed sinks,
--
(cherry picked from commit d222b5cd3d2e9f53fbf9810c565f9b82739d0154)

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

...

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

...

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

...

  • 400.1 Bring down link: s1 to h1 - PASS (tick)
  • 400.2 Check intent states - PASS (tick)FAIL (error)
    • Not all Intents in installed state
  • 400.3 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 400.4 Adding link: s1 to h1. - PASS (tick)
  • 400.5 Check intent states - PASS (tick)FAIL (error)
    • Not all Intents in installed state
  • 400.6 Testing connectivity... - FAIL (error)
    • Connectivity is NOT as expected.