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/1162/

...

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 bfe554098cfe08daa241c1d3c0e7cca3210c9334 77958a5941bfa989f54858dee5515e137676e3db (HEAD -] master, origin/master, origin/HEAD)
Author: Andrea Campanella [andrea@opennetworking.orgHarshada Chaundkar [Harshada_Chaundkar@comcast.com]
AuthorDate: Sun Sep 8 10:16:01 2019 -0700Mon Aug 5 15:33:30 2019 +0000
Commit: Andrea Campanella pier [andrea@opennetworkingpier@opennetworking.org]
CommitDate: Sun Mon Sep 8 1816 16:0150:53 42 2019 +0000
Fix for modulation display and power strings-0700

Adding ACL flow for Table 60 for Ipv6

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

...

Set up ONOS with 3 node(s) ONOS cluster

...

-

...

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)

Case 100: Bring down one host at a time and test connectivity. - FAIL

...

  • Not all Intents in installed state

...

  • Not all Intents in installed state

...

FAIL

...

  • Not all Intents in installed state

...

  • Not all Intents in installed state

...

  • Not all Intents in installed state

...

  • Not all Intents in installed state

...

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

Case 400: Bring down one link at a time and test connectivity. - FAIL

...

  • Not all Intents in installed state

...

  • Connectivity failed.

...

  • Not all Intents in installed state

...