Page History

...

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

commit d7ed697f2bce79022b33e8f49ba461182046b172 8b5599b802c1aa3f43e5f01564853c946439c77a (HEAD -] master, origin/master, origin/HEAD)
Author: Ray Milkey Jian Li [ray@opennetworkingpyguni@gmail.orgcom]
AuthorDate: Thu Mon Nov 15 19 18:2445:22 46 2018 -0800+0900
Commit: Ray Milkey Thomas Vachuska [ray@opennetworkingtom@opennetworking.org]
CommitDate: Thu Mon Nov 15 2019 21:0751:13 2018 -0800
Handle IllegalArgumentException from packet parsing+0000

Fix: enforce to synchronize all flow rules in case sync failures

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

...

• 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 - FAIL PASS
• 4.8 Check onoscli devices have ovs 10.192.19.231 - FAIL PASS

Case 2: Test ovsdb connection and teardown - PASS

...