Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
...
HTML |
---|
<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/FUNCovsdbtest_onos-2.2_20-builds_graph.jpg", alt="FUNCovsdbtest", style="width:525px;height:350px;border:0"> |
commit 212dc2fe85aa940c92f2c9e2f8d20ca064f157af a30877e1eb778f32d5f5201ab5c255bc9d97c195 (HEAD -] onos-2.2, origin/onos-2.2)
Author: Carmelo Cascone Andrea Campanella [carmelo@opennetworkingandrea@opennetworking.org]
AuthorDate: Thu Nov 21 2228 14:1331:09 02 2019 -0800+0100
Commit: Carmelo Cascone Andrea Campanella [carmelo@opennetworkingandrea@opennetworking.org]
CommitDate: Thu Fri Nov 21 2229 17:1306:09 2019 -0800
Replace references to old versions of Bazel with 1.015 2019 +0000
Avoid propagating a null chassisID
--
(cherry picked from commit f468858e9104e49e83c6294fdc4d17ce9456d7fd)
Case 1: Starting
...
up
...
1 node(s) ONOS cluster
...
-
...
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
...