Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

commit fb7e787d47d59a1129f1bbd4f1f3d43b20c8af99 9e1e5df971f13c98a61fcdee768d90f6c6367684 (HEAD, origin/master, origin/HEAD, masteronos-2.5, onos-2.5)
Author: Wailok Shum Daniele Moro [wailok@opennetworkingdaniele@opennetworking.org]
AuthorDate: Fri Thu Jun 24 18:17:30 :08 2021 +08000200
Commit: Pier Luigi Ventre [pier@opennetworkingDaniele Moro [daniele@opennetworking.org]
CommitDate: Mon Fri Jun 21 1625 13:3220:31 08 2021 +0000

[SDFAB-102] Backport changes required for policies to fabric.p4 (Redirect)256] Add CLI command for reading content of the UPF store

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

Set up ONOS with 5 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 - FAIL (error)
    • Something is wrong with app Ids
  • 1.15 Install onos-ovsdb - FAIL (error)
    • Install onos-ovsdatabase failed
  • 1.16 Install onos-app-vtn - FAIL (error)
    • Install onos-app-vtn failed

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.128.99.28 - PASS (tick)
  • 3.2 ovsdb node 2 set ovs manager to 10.128.99.28 - PASS (tick)
  • 3.3 Check ovsdb node 1 manager is 10.128.99.28 - PASS (tick)
  • 3.4 Check ovsdb node 2 manager is 10.128.99.28 - PASS (tick)
  • 3.5 Check default br-int bridge on ovsdb node 10.128.99.27 - FAIL (error)
    • onos add default bridge on the node 1 failed
  • 3.6 Check default br-int bridge on ovsdb node 10.128.99.28 - FAIL (error)
    • onos add default bridge on the node 2 failed
  • 3.7 Check default vxlan port on ovsdb node 10.128.99.27 - FAIL (error)
    • onos add default vxlan port on the node 1 failed
  • 3.8 Check default vxlan port on ovsdb node 10.128.99.28 - FAIL (error)
    • onos add default vxlan port on the node 2 failed

Case 4: - No Result

  • 4.1 ovsdb node 1 set ovs manager to 10.128.99.28 - PASS (tick)
  • 4.2 ovsdb node 2 set ovs manager to 10.128.99.28 - PASS (tick)
  • 4.3 Check ovsdb node 1 manager is 10.128.99.28 - PASS (tick)
  • 4.4 Check ovsdb node 2 manager is 10.128.99.28 - PASS (tick)
  • 4.5 Check ovsdb node 1 bridge br-int controller set to 10.128.99.28 - FAIL (error)
    • Check ovsdb node 1 bridge br-int controller set to 10.128.99.28 failed
    • sudo ovs-vsctl show
    • 8065eb82-7314-404b-81a8-6560799c5e4e
    • Manager "tcp:10.128.99.28:6640"
    • sdn@prodVM-TestStation:~$
  • 4.6 Check ovsdb node 2 bridge br-int controller set to 10.128.99.28 - PASS (tick)