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

...

commit fedad5b2b65499ad534b6e90568b5478387b7742 b5e6e06634aa4831aad387007531183a77c007f1 (HEAD, origin/master, origin/HEAD, master)
Author: Jordan Halterman [jordan@opennetworking.orgYuta HIGUCHI [y-higuchi@ak.jp.nec.com]
AuthorDate: Mon Oct 9 23:16:27 Nov 6 18:14:44 2017 -07000800
Commit: Thomas Vachuska Ray Milkey [tom@opennetworkingray@opennetworking.org]
CommitDate: Tue Oct 31 23:07:21 Nov 7 15:32:16 2017 +0000
[ONOS-7083] Update application versions and activate active applications on upgrade
maven fix for netty-native stuff

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.

...

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

...