FUNCovsdbtest at 31 Dec 2018 20:35:32
![FUNCovsdbtest](https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/FUNCovsdbtest_master_20-builds_graph.jpg)
commit 50855cf1fa9e81fd89d9857d2a0c2f538071592e (HEAD -] master, origin/master, origin/HEAD)
Author: Sean Condon [sean.condon@microsemi.com]
AuthorDate: Sun Dec 23 15:37:42 2018 +0000
Commit: Sean Condon [sean.condon@microsemi.com]
CommitDate: Fri Dec 28 20:25:53 2018 +0000
Enable link functionality in GUI2 Topology View
Case 1: Starting up 1 node(s) ONOS cluster - PASS
Set up ONOS with 1 node(s) ONOS cluster
- 1.1 Constructing test variables - No Result
- 1.2 Constructing test variables - PASS
- 1.3 Apply cell to environment - PASS
- 1.4 Uninstalling Atomix - PASS
- 1.5 Uninstalling ONOS package - PASS
- 1.6 Creating ONOS package - PASS
- 1.7 Installing Atomix - PASS
- 1.8 Installing ONOS package - PASS
- 1.9 Set up ONOS secure SSH - PASS
- 1.10 Checking ONOS service - PASS
- 1.11 Starting ONOS CLI sessions - PASS
- 1.12 Checking ONOS nodes - PASS
- 1.13 Checking ONOS applications - PASS
- 1.14 App Ids check - PASS
- 1.15 Install onos-ovsdb - PASS
- 1.16 Install onos-app-vtn - PASS
Case 3: Test default br-int configuration and vxlan port - 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
- 3.2 ovsdb node 2 set ovs manager to 10.192.19.231 - PASS
- 3.3 Check ovsdb node 1 manager is 10.192.19.231 - PASS
- 3.4 Check ovsdb node 2 manager is 10.192.19.231 - PASS
- 3.5 Check default br-int bridge on ovsdb node 10.192.19.229 - FAIL
- onos add default bridge on the node 1 failed
- 3.6 Check default br-int bridge on ovsdb node 10.192.19.231 - FAIL
- onos add default bridge on the node 2 failed
- 3.7 Check default vxlan port on ovsdb node 10.192.19.229 - FAIL
- onos add default vxlan port on the node 1 failed
- 3.8 Check default vxlan port on ovsdb node 10.192.19.231 - FAIL
- 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
- 4.2 ovsdb node 2 set ovs manager to 10.192.19.231 - PASS
- 4.3 Check ovsdb node 1 manager is 10.192.19.231 - PASS
- 4.4 Check ovsdb node 2 manager is 10.192.19.231 - PASS
- 4.5 Check ovsdb node 1 bridge br-int controller set to 10.192.19.231 - FAIL
- 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
- 4.7 Check onoscli devices have ovs 10.192.19.229 - PASS
- 4.8 Check onoscli devices have ovs 10.192.19.231 - PASS
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
- 2.2 Check ovsdb node manager is 10.192.19.231 - PASS
- 2.3 Delete ovsdb node manager - PASS
- 2.4 Check ovsdb node delete manager 10.192.19.231 - PASS
Case 5: - FAIL
- 5.1 ovsdb node 1 set ovs manager to onos - PASS
- 5.2 Check ovsdb node 1 manager is 10.192.19.231 - PASS
- 5.3 Check ovsdb node 1 bridge br-int default flows on 10.192.19.229 - FAIL
Case 6: Configure Network Subnet Port - PASS
Configure Network Subnet Port Verify post is OK
- 6.1 Generate Post Data - No Result
- 6.2 Post Network Data via HTTP(Post port need post network) - PASS
- 6.3 Post Subnet Data via HTTP(Post port need post subnet) - PASS
- 6.4 Post Port1 Data via HTTP - PASS
- 6.5 Post Port2 Data via HTTP - PASS
Case 7: - FAIL
- 7.1 ovsdb node 1 set ovs manager to 10.192.19.231 - PASS
- 7.2 ovsdb node 2 set ovs manager to 10.192.19.231 - PASS
- 7.3 Create host1 on node 1 10.192.19.229 - PASS
- 7.4 Create host2 on node 2 10.192.19.231 - PASS
- 7.5 Create port on host1 on the node 10.192.19.229 - PASS
- 7.6 Create port on host2 on the node 10.192.19.231 - PASS
- 7.7 Add port to ovs br-int and host go-online on the node 10.192.19.229 - PASS
- 7.8 Add port to ovs br-int and host go-online on the node 10.192.19.231 - PASS
- 7.9 Check onos set host flows on the node 10.192.19.229 - FAIL
- 7.10 Check onos set host flows on the node 10.192.19.231 - PASS
- 7.11 Check hosts can ping each other - FAIL
Case 8: - FAIL
- 8.1 Delete ovsdb node 1 manager - PASS
- 8.2 Delete ovsdb node 2 manager - PASS
- 8.3 Delete ovsdb node 1 bridge br-int - PASS
- 8.4 Delete ovsdb node 2 bridge br-int - PASS
- 8.5 Delete ip netns host on the ovsdb node 1 - PASS
- 8.6 Delete ip netns host on the ovsdb node 2 - PASS
- 8.7 Check onoscli devices openflow session is false 10.192.19.229 - FAIL
- 8.8 Check onoscli devices have ovs 10.192.19.231 - FAIL