Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published from Jenkins build: https://jenkins.onosproject.org/job/FUNC-pipeline-master/1623/

...

HTML
<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/FUNCovsdbtest_masteronos-1.15_20-builds_graph.jpg", alt="FUNCovsdbtest", style="width:525px;height:350px;border:0">

commit 71ba99f75a206c2875c43a2a1b5ff45415aea8f7 fb73f668dab68515cae00533f006067d068da7e1 (HEAD -] masteronos-1.15, origin/master, origin/HEADonos-1.15)
Author: Carmelo Cascone Charles Chan [carmelo@opennetworkingrascov@gmail.orgcom]
AuthorDate: Thu Oct 24 1617 20:3409:02 45 2019 -0700
Commit: Carmelo Cascone Charles Chan [carmelo@opennetworkingrascov@gmail.orgcom]
CommitDate: Thu Oct 31 16:31:22 2019 +0000
Bazel workspace cleanupFri Nov 1 13:12:17 2019 -0700

Added table miss flow for ovs-ofdpa punt table

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

...

Set up ONOS with 1 node(s) ONOS cluster

  • 1.1 Constructing test variables - No Result (warning)
  • 1.2 Constructing test variables - PASS (tick)
  • 1.3 Apply cell to environment - PASS (tick)
  • 1.4 Uninstalling Atomix - PASS (tick)
  • 1.5 Uninstalling ONOS package - PASS (tick)
  • 1.6 Creating ONOS package - PASS (tick)
  • 1.7 Installing Atomix - PASS (tick)
  • 1.8 Installing ONOS package - PASS (tick)
  • 1.9 Set up ONOS secure SSH - PASS (tick)
  • 1.10 Checking ONOS service - PASS (tick)
  • 1.11 Starting ONOS CLI sessions - PASS (tick)
  • 1.12 Checking ONOS nodes - PASS (tick)
  • 1.13 Checking ONOS applications - PASS (tick)
  • 1.14 App Ids check - PASS (tick)
  • 1.15 Install onos-ovsdb - PASS (tick)
  • 1.16 Install onos-app-vtn - PASS (tick)

...

FAIL

...

onos create default br-int bridge and vxlan port on the ovsdb node

  • 3.1 ovsdb node 1 set ovs manager to 10.192.19.231 - PASS (tick)
  • 3.2 ovsdb node 2 set ovs manager to 10.192.19.231 - PASS (tick)
  • 3.3 Check ovsdb node 1 manager is 10.192.19.231 - PASS (tick)
  • 3.4 Check ovsdb node 2 manager is 10.192.19.231 - PASS (tick)
  • 3.5 Check default br-int bridge on ovsdb node 10.192.19.229 - FAIL (error)
    • onos add default bridge on the node 1 failed
  • 3.6 Check default br-int bridge on ovsdb node 10.192.19.231 - FAIL (error)
    • onos add default bridge on the node 2 failed
  • 3.7 Check default vxlan port on ovsdb node 10.192.19.229 - FAIL (error)
    • onos add default vxlan port on the node 1 failed
  • 3.8 Check default vxlan port on ovsdb node 10.192.19.231 - FAIL (error)
    • onos add default vxlan port on the node 2 failed

Case 4: - FAIL

  • 4.1 ovsdb node 1 set ovs manager to 10.192.19.231 - PASS (tick)
  • 4.2 ovsdb node 2 set ovs manager to 10.192.19.231 - PASS (tick)
  • 4.3 Check ovsdb node 1 manager is 10.192.19.231 - PASS (tick)
  • 4.4 Check ovsdb node 2 manager is 10.192.19.231 - PASS (tick)
  • 4.5 Check ovsdb node 1 bridge br-int controller set to 10.192.19.231 - FAIL (error)
    • sudo ovs-vsctl show
    • 69d75e74-ec31-40a6-9908-c1fc20d9faab
    • is_connected: true
    • sdn@new-prod-test-station:~$
  • 4.6 Check ovsdb node 2 bridge br-int controller set to 10.192.19.231 - PASS (tick)
  • 4.7 Check onoscli devices have ovs 10.192.19.229 - PASS (tick)
  • 4.8 Check onoscli devices have ovs 10.192.19.231 - PASS (tick)

Case 2: Test ovsdb connection and teardown - PASS

Test ovsdb connection create and delete over ovsdb node and onos node

  • 2.1 Set ovsdb node manager - PASS (tick)
  • 2.2 Check ovsdb node manager is 10.192.19.231 - PASS (tick)
  • 2.3 Delete ovsdb node manager - PASS (tick)
  • 2.4 Check ovsdb node delete manager 10.192.19.231 - PASS (tick)

Case 5: - FAIL

  • 5.1 ovsdb node 1 set ovs manager to onos - PASS (tick)
  • 5.2 Check ovsdb node 1 manager is 10.192.19.231 - PASS (tick)
  • 5.3 Check ovsdb node 1 bridge br-int default flows on 10.192.19.229 - FAIL (error)

Case 6: Configure Network Subnet Port - PASS

Configure Network Subnet Port Verify post is OK

  • 6.1 Generate Post Data - No Result (warning)
  • 6.2 Post Network Data via HTTP(Post port need post network) - PASS (tick)
  • 6.3 Post Subnet Data via HTTP(Post port need post subnet) - PASS (tick)
  • 6.4 Post Port1 Data via HTTP - PASS (tick)
  • 6.5 Post Port2 Data via HTTP - PASS (tick)

Case 7: - FAIL

  • 7.1 ovsdb node 1 set ovs manager to 10.192.19.231 - PASS (tick)
  • 7.2 ovsdb node 2 set ovs manager to 10.192.19.231 - PASS (tick)
  • 7.3 Create host1 on node 1 10.192.19.229 - PASS (tick)
  • 7.4 Create host2 on node 2 10.192.19.231 - PASS (tick)
  • 7.5 Create port on host1 on the node 10.192.19.229 - PASS (tick)
  • 7.6 Create port on host2 on the node 10.192.19.231 - PASS (tick)
  • 7.7 Add port to ovs br-int and host go-online on the node 10.192.19.229 - PASS (tick)
  • 7.8 Add port to ovs br-int and host go-online on the node 10.192.19.231 - PASS (tick)
  • 7.9 Check onos set host flows on the node 10.192.19.229 - FAIL (error)
  • 7.10 Check onos set host flows on the node 10.192.19.231 - PASS (tick)
  • 7.11 Check hosts can ping each other - FAIL (error)

Case 8: - FAIL

...