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/FUNCnetCfg/953/

...

commit a9b42eabd74f2d2372d20d9fd2d6b97b14d44292 52f5828004e9c59774a94542e74af7dcc18d9771 (HEAD, origin/onos-1.9, onos-1.9)
Author: Jordan Halterman Ray Milkey [jordan@onlabray@onlab.us]
AuthorDate: Wed Apr 26 Fri Jun 23 12:4146:31 32 2017 -0700
Commit: Ray Milkey [ray@onlab.us]
CommitDate: Fri May 5 13:28:45 Jun 23 12:46:32 2017 -0700
[ONOS-6345] Track tombstones within transactions for optimistic locking on null values
Starting snapshot 1.9.3-SNAPSHOT

Case 1: Constructing test variables and building ONOS package - PASS

...

  • 2.1 Apply cell to environment - PASS (tick)
  • 2.2 Creating ONOS package - PASS (tick)
  • 2.3 Uninstalling ONOS package - PASS (tick)
  • 2.4 Installing ONOS package - PASS (tick)
  • 2.5 Starting ONOS service - PASS (tick)

Case 20: Add Network configurations to the cluster -

...

PASS

Add Network Configurations for devices not discovered yet. One device is allowed, the other disallowed.

  • 20.1 Add Net Cfg for switch1 - PASS (tick)
  • 20.2 Add Net Cfg for switch3 - PASS (tick)
  • 20.3 Check net config - FAIL (error)
    • Net Cfg is different on some nodes. Some nodes failed to GET netCfg.
  • PASS (tick)

Case 11: Start Mininet topology with OF 1.3 switches - PASS

...

  • 11.1 Starting Mininet topology with OF 1.3 switches - PASS (tick)

Case 27: Posting network configurations to the top level web resource -

...

PASS

  • 27.1 Get json object from Net Cfg - No Result (warning)
  • 27.2 Posting json object to Net Cfg - No Result (warning)
  • 27.3 Compare device with ONOS - No Result (warning)
  • 27.4 Check net config - FAIL (error)
    • Net Cfg is different on some nodes. Some nodes failed to GET netCfg.
  • PASS (tick)
  • 27.5 ONOS should only show devices S1, S2, S4, S5 and S6 - FAIL (error)
    • ONOS devices doesn't match the list of allowed devices.
    • Expected devices: ['of:0000000000000001', 'of:0000000000000002', 'of:0000000000000004', 'of:0000000000000005', 'of:0000000000000006']
    • Actual devices: []
  • PASS (tick)
  • 27.6 Modify json object so S6 is disallowed - PASS (tick)

Case 26: Check to see if the pre-startup configurations were set, then remove their allowed status -

...

PASS

  • 26.1 Checking configurations for Switches 5 and 6 - No Result (warning)
  • 26.2 ONOS should only show devices S1, S2, S4, and S5 - FAIL (error)
  • ONOS devices doesn't match the list of allowed devices
  • PASS (tick)
  • 26.3 Removing allowed status from Switches 5 and 6 - No Result (warning)

Case 21: Check Devices After they initially connect to ONOS -

...

PASS

  • 21.1 Check net config - FAIL (error)
    • Net Cfg is different on some nodes. Some nodes failed to GET netCfg.
  • PASS (tick)
  • 21.2 ONOS should only show devices S1, S2, and S4 - FAIL (error)
    • ONOS devices doesn't match the list of allowed devices
  • PASS (tick)
  • 21.3 Check device annotations - FAIL (error)
  • Incorrect annotations for configured devices.
  • PASS (tick)

Case 22: Add Network configurations for connected devices to the cluster -

...

PASS

Add Network Configurations for discovered devices. One device is allowed, the other disallowed.

  • 22.1 Add Net Cfg for switch2 - PASS (tick)
  • 22.2 Add Net Cfg for switch4 - FAIL (error)
    • Net Cfg for device s4 not correctly set
  • PASS (tick)
  • 22.3 Check net config - FAIL (error)
    • Net Cfg is different on some nodes. Some nodes failed to GET netCfg.
  • PASS (tick)

Case 23: Check Devices after all configurations are set -

...

PASS

  • 23.1 Check net config - FAIL (error)
    • Net Cfg is different on some nodes. Some nodes failed to GET netCfg.
  • PASS (tick)
  • 23.2 ONOS should only show devices S1 and S2 - FAIL (error)
    • ONOS devices doesn't match the list of allowed devices.
    • Expected devices: ['of:0000000000000001', 'of:0000000000000002']
    • Actual devices: []
  • PASS (tick)
  • 23.3 Check device annotations - FAIL (error)
    • Incorrect annotations for configured devices.
  • PASS (tick)

Case 24: Testing removal of configurations -

...

PASS

  • 24.1 Remove 'allowed' configuration from all devices - FAIL (error)
    • Failed to remove the 'allowed' config key.
  • PASS (tick)
  • 24.2 Check net config - FAIL (error)
    • Net Cfg is different on some nodes. Some nodes failed to GET netCfg.
  • PASS (tick)
  • 24.3 Delete basic config for s1 and s2 - PASS (tick)
  • 24.4 Check net config - FAIL (error)
  • Net Cfg is different on some nodes. Some nodes failed to GET netCfg.
  • PASS (tick)
  • 24.5 Delete the net config for S3 - FAIL (error)
  • Failed to removed S3's config
  • PASS (tick)
  • 24.6 Check net config - FAIL (error)
    • Net Cfg is different on some nodes. Some nodes failed to GET netCfg.
  • PASS (tick)
  • 24.7 Delete the net config for all devices - FAIL (error)
    • Failed to remove device config
  • PASS (tick)
  • 24.8 Check net config - FAIL (error)
    • Net Cfg is different on some nodes. Some nodes failed to GET netCfg.
  • PASS (tick)
  • 24.9 Assert the net config for devices is empty - FAIL (error)
  • Failed to remove device config
  • PASS (tick)