Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published from Jenkins build: https://jenkins.onosproject.org/job/FUNC-pipeline-master/1354/

...

HTML
<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 1e39bd2f4444f6662898a936fa1944d5aa35718e 02fb583e9e5fda3be2f137b23284ef8ef7d0b5d3 (HEAD -] master, origin/master, origin/HEAD)
Author: Thomas Vachuska Jordan Halterman [tom@opennetworkingjordan@opennetworking.org]
AuthorDate: Fri Mon Dec 14 1417 15:4752:53 34 2018 -0800
Commit: Thomas Vachuska Ray Milkey [tom@opennetworkingray@opennetworking.org]
CommitDate: Fri Tue Dec 14 1418 02:4749:53 31 2018 -0800
Allowing cell-stc to inherit stcOpenJDK env. variable.+0000

Upgrade to Atomix 3.1.0-rc1

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

...

  • 3.1 ovsdb node 1 set ovs manager to 10.192.19.231 - PASS (tick)
  • 3.2 ovsdb node 2 set ovs manager to 10.192.19.231 - PASS (tick)
  • 3.3 Check ovsdb node 1 manager is 10.192.19.231 - PASS (tick)
  • 3.4 Check ovsdb node 2 manager is 10.192.19.231 - PASS (tick)
  • 3.5 Check default br-int bridge on ovsdb node 10.192.19.229 - FAIL (error)
    • onos add default bridge on the node 1 failed
  • 3.6 Check default br-int bridge on ovsdb node 10.192.19.231 - FAIL (error)
    • onos add default bridge on the node 2 failed
  • 3.7 Check default vxlan port on ovsdb node 10.192.19.229 - FAIL (error)
    • onos add default vxlan port on the node 1 failed
  • 3.8 Check default vxlan port on ovsdb node 10.192.19.231 - FAIL (error)
    • 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 (tick)
  • 4.2 ovsdb node 2 set ovs manager to 10.192.19.231 - PASS (tick)
  • 4.3 Check ovsdb node 1 manager is 10.192.19.231 - PASS (tick)
  • 4.4 Check ovsdb node 2 manager is 10.192.19.231 - PASS (tick)
  • 4.5 Check ovsdb node 1 bridge br-int controller set to 10.192.19.231 - PASS (tick)- FAIL (error)
    • 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 (tick)
  • 4.7 Check onoscli devices have ovs 10.192.19.229 - PASS (tick)
  • 4.8 Check onoscli devices have ovs 10.192.19.231 - PASS (tick)

...

  • 7.1 ovsdb node 1 set ovs manager to 10.192.19.231 - PASS (tick)
  • 7.2 ovsdb node 2 set ovs manager to 10.192.19.231 - PASS (tick)
  • 7.3 Create host1 on node 1 10.192.19.229 - PASS (tick)
  • 7.4 Create host2 on node 2 10.192.19.231 - PASS (tick)
  • 7.5 Create port on host1 on the node 10.192.19.229 - PASS (tick)
  • 7.6 Create port on host2 on the node 10.192.19.231 - PASS (tick)
  • 7.7 Add port to ovs br-int and host go-online on the node 10.192.19.229 - PASS (tick)
  • 7.8 Add port to ovs br-int and host go-online on the node 10.192.19.231 - PASS (tick)
  • 7.9 Check onos set host flows on the node 10.192.19.229 - PASS (tick)FAIL (error)
  • 7.10 Check onos set host flows on the node 10.192.19.231 - PASS (tick)
  • 7.11 Check hosts can ping each other - FAIL (error)

...