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_BM/2736/

...

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

commit c29f74827d1f6650620335c1ce5a7e9f5c6a5b6e 132393a4a23dba0706fb6e19fb787561d83d69bc (HEAD, origin/master, origin/HEAD, master)
Author: Ray Milkey Charles Chan [ray@opennetworkingrascov@gmail.orgcom]
AuthorDate: Fri Dec 22 16:38:08 2017 +0000Thu Jan 4 14:26:07 2018 -0800
Commit: Ray Milkey Charles Chan [ray@opennetworkingrascov@gmail.orgcom]
CommitDate: Fri Dec 22 19:22:05 2017 +0000
Revert "Bump up buck version"
--
This reverts commit e743babd01c5cbfc3f580a4c77993bc7047d0846.
Change-Id: Ida34fc6fb6faba624b93b9b01a98e9f5d2bb4d33Tue Jan 9 13:55:27 2018 -0800

CORD-2470 Fix NPEs

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: -

...

FAIL

  • 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)FAIL (error)
    • Connectivity is not as expected
  • 2.8 Loading vpls configuration in case any configuration was missed. - PASS (tick)

Case 50: Check connectivity before running all other tests. -

...

FAIL

  • 50.1 Check intent states - PASS (tick)FAIL (error)
    • Not all Intents in installed state
  • 50.2 Testing connectivity... - PASS (tick)FAIL (error)
    • Connectivity is NOT as expected.

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

...