Have questions? Stuck? Please check our FAQ for some common questions and answers.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 644 Next »

FUNCnetconf at 16 Aug 2018 22:01:02

FUNCnetconf

commit 7981a32f37d64225a5b641725ba172cdc32e2f0d (HEAD -] master, origin/master, origin/HEAD)
Author: Ray Milkey [ray@opennetworking.org]
AuthorDate: Thu Aug 16 14:55:46 2018 -0700
Commit: Ray Milkey [ray@opennetworking.org]
CommitDate: Thu Aug 16 23:52:44 2018 +0000

Fix NPE when component can't be found

Case 1: Pull onos branch and build onos on Teststation. - PASS

For loading from params file, and pull and build the latest ONOS package

  • 1.1 Constructing test variables - PASS (tick)

Case 2: Starting up 1 node(s) ONOS cluster - FAIL

Set up ONOS with 1 node(s) ONOS cluster

  • 2.1 Apply cell to environment - PASS (tick)
  • 2.2 Uninstalling Atomix - PASS (tick)
  • 2.3 Uninstalling ONOS package - PASS (tick)
  • 2.4 Creating ONOS package - PASS (tick)
  • 2.5 Installing Atomix - PASS (tick)
  • 2.6 Installing ONOS package - PASS (tick)
  • 2.7 Set up ONOS secure SSH - FAIL (error)
    • Test step FAIL
  • 2.8 Checking ONOS service - FAIL (error)
    • ONOS service did not start properly on all nodes
  • 2.9 Starting ONOS CLI sessions - PASS (tick)
  • 2.10 Checking ONOS nodes - FAIL (error)
    • Not all ONOS nodes are in READY state
  • 2.11 Checking ONOS applications - FAIL (error)
    • Nodes check failed.

Case 100: Start up NETCONF app in all nodes Test - 1 NODE(S) - FAIL

  • No labels