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 0ee285a8fb9ff3362d11cf40fc37602cc1b1465d d95d3524caff5449aded4ff9397c3ed717fc91e6 (HEAD -] , origin/onos-2.2, origin/ onos-2.2)
Author: pier Jian Li [pier@opennetworkingpyguni@gmail.orgcom]
AuthorDate: Fri Apr 3 Thu Aug 12 18:4403:21 2020 30 2021 +02000900
Commit: Pier Luigi Ventre [pier@opennetworking.orgJian Li [pyguni@gmail.com]
CommitDate: Fri Apr 17 13:43:38 2020 +0000
[ONOS-8086] Groups entries are not deletedThu Aug 12 18:58:19 2021 +0900
Add default route option to kubevirt network
Case 1: Starting up
...
5 node(s) ONOS cluster
...
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
...
-
...
FAIL
...
Case 8: - FAIL
...