FUNCnetCfg at 16 Aug 2018 21:29:17
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
Case 25: Preparing network-cfg.json to load configurations - PASS
- 25.1 Moving network-cfg.json to $ONOS_ROOT/tools/package/config/ - PASS
Case 2: Starting up 3 node(s) ONOS cluster - FAIL
Set up ONOS with 3 node(s) ONOS cluster
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling Atomix - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.4 Creating ONOS package - PASS
- 2.5 Installing Atomix - PASS
- 2.6 Installing ONOS package - PASS
- 2.7 Set up ONOS secure SSH - FAIL
- Test step FAIL
- 2.8 Checking ONOS service - FAIL
- ONOS service did not start properly on all nodes
- 2.9 Starting ONOS CLI sessions - PASS
- 2.10 Checking ONOS nodes - FAIL
- Not all ONOS nodes are in READY state
- 2.11 Checking ONOS applications - FAIL
- Not all ONOS apps are activated
Case 20: Add Network configurations to the cluster - FAIL
Add Network Configurations for devices not discovered yet. One device is allowed, the other disallowed.
- 20.1 Add Net Cfg for switch1 - FAIL
- Net Cfg for device s1 not correctly set
- 20.2 Add Net Cfg for switch3 - FAIL
- Net Cfg for device s3 not correctly set
- 20.3 Check net config - FAIL
- Check Net Cfg failed. Check above messages.
Case 11: Start Mininet topology with OF 1.3 switches - PASS
Start mininet topology with OF 1.3 switches to test intents, exits out if topology did not start correctly
- 11.1 Starting Mininet topology with OF 1.3 switches - PASS
Case 27: Posting network configurations to the top level web resource - No Result
- 27.1 Get json object from Net Cfg - No Result