Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published from Jenkins build: https://onos-jenkins.onlab.us/job/Pipeline_postjob_VM/1408/

...

HTML
<img src="https://onos-jenkins.onlab.us/job/Pipeline_postjob_BM/lastSuccessfulBuild/artifact/VPLSfailsafe_onos-1.12_20-builds_graph.jpg", alt="VPLSfailsafe", style="width:525px;height:350px;border:0">

commit 21a2dc89fdf11f5a40a0b8d10281a8f57b2679dc 73a6cc193e30c7669d7fe85b81922a2712bce1bc (HEAD, origin/onos-1.12, onos-1.12)
Author: Yi Tseng Saurav Das [yi@opennetworkingsauravdas@alumni.orgstanford.edu]
AuthorDate: Wed Nov 29 14:39:18 Tue Dec 5 15:00:23 2017 -0800
Commit: Yi Tseng Charles Chan [yi@opennetworkingrascov@gmail.orgcom]
CommitDate: Fri Tue Dec 1 225 18:4635:36 01 2017 +0000
[CORD-2320] DHCPv4 thows an exception when no indirect DHCPv4 server is configured
-0800

Fix for empty flooding groups due to bucket add/remove commands being reordered, and

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

...

  • 1.1 Constructing test variables - PASS (tick)
  • 1.2 Apply cell to environment - PASS (tick)
  • 1.3 Uninstalling ONOS package - PASS (tick)
  • 1.4 Creating ONOS package - PASS (tick)
  • 1.5 Installing ONOS package - PASS (tick)
  • 1.6 Set up ONOS secure SSH - PASS (tick)
  • 1.7 Checking ONOS service - PASS (tick)
  • 1.8 Starting ONOS CLI sessions - PASS (tick)
  • 1.9 Starting Mininet - PASS (tick)
  • 1.10 Activate apps defined in the params file - No Result (warning)
  • 1.11 Set ONOS configurations - No Result (warning)
  • 1.12 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 - FAIL (error)
    • Connectivity is not as expected
  • 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 - FAIL (error)
    • Not all Intents in installed state
  • PASS (tick)
  • 50.2 Testing connectivity... - FAIL (error)
    • Connectivity is NOT as expected.
  • PASS (tick)

Case 100: Bring down one host at a time and test connectivity. - 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... - FAIL (error)
    • Connectivity failed.
  • 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 - FAIL (error)
    • Not all Intents in installed state
  • PASS (tick)
  • 100.7 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.

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