Versions Compared

Old Version 769

changes.mady.by.user Jenkins Technical User

Saved on

compared with

New Version 770

changes.mady.by.user Jenkins Technical User

Saved on

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/FUNCintentRest_master_20-builds_graph.jpg", alt="FUNCintentRest", style="width:525px;height:350px;border:0">

commit e98dead599045c3f51d650afdac07d305418c8b6 c6f2f7f3c529217850ecd32e12a211f8c3e3fc64 (HEAD, origin/master, origin/HEAD, master)
Author: Carmelo Cascone Daniele Moro [carmelo@opennetworkingdaniele@opennetworking.org]
AuthorDate: Thu Jan 28 Fri Dec 18 10:25:59 2021 -080055:57 2020 +0100
Commit: pierventre Daniele Moro [pier@opennetworkingdaniele@opennetworking.org]
CommitDate: Tue Fri Feb 2 085 19:4103:08 05 2021 +0100
Fix issues seen during bundle refresh with shared executors
Add Optional match fields support to PI subsystem

Case 1: Pull onos branch and build onos on Teststation. - PASS

...

  • 17.1 Enabling Flow Objectives - PASS (tick)

Case 1000: Host Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Objectives -

...

PASS

This test case tests Host intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Objectives

  • 1000.1 IPV4: Add and test host intents between h1 and h9 - FAIL (error)
    • Assertion result for IPV4 host intent with mac addresses
    • Install Intent State Failed
  • PASS (tick)
  • 1000.2 DUALSTACK1: Add host intents between h3 and h11 - FAIL (error)
    • Assertion Result for dualstack IPV4 with MAC addresses
    • Install Intent State Failed
  • PASS (tick)
  • 1000.3 1000.3 DUALSTACK2: Add host intents between h1 and h11 - FAIL (error)
  • Assertion Result for dualstack2 host intent
    • Install Intent State Failed
  • PASS (tick)
  • 1000.4 1HOP: Add host intents between h1 and h3 - FAIL (error)
  • Assertion Result for 1HOP for IPV4 same switch
    • Install Intent State Failed
  • PASS (tick)
  • 1000.5 VLAN1: Add vlan host intents between h4 and h12 - FAIL (error)
    • Assertion Result vlan IPV4
    • Install Intent State Failed
  • PASS (tick)
  • 1000.6 Confirm that ONOS leadership is unchanged - FAIL (error)
    • ONOS Leader Mismatch
  • PASS (tick)

Case 2000: Point Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Objectives - PASS

This test case will test point to point intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Objectives

  • 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS (tick)
  • 2000.1 NOOPTION: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for NOOPTION point intent
    • Install Intent State Failed
  • 2000.2 IPV4: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for IPV4 point intent
    • Install Intent State Failed
  • PASS (tick)
  • 2000.3 IPV4_2: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for IPV4 no mac address point intents
    • Install Intent State Failed
  • PASS (tick)
  • 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.5 SDNIP-TCP 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
    Install Intent State Failed
  • PASS (tick)
  • 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)
  • 2000.7 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.8 1HOP: Add point intents between h1 and h3 - PASS (tick)

Case 3000: Single to Multi Point Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Objectives - FAIL

This test case will test single point to multi point intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Objectives

  • 3000.1 NOOPTION: Install and test single point to multi point intents - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with no options set
  • 3000.2 IPV4: Install and test single point to multi point intents - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses
  • 3000.3 IPV4_2: Add single point to multi point intents - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with IPV4 type and no MAC addresses
  • 3000.4 VLAN: Add single point to multi point intents - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses in the same VLAN
  • 3000.5 VLAN: Add single point to multi point intents - FAIL (error)
    • Assertion results for single to multi point intent with VLAN treatment

Case 5000: Test host mobility with host intents - PASS

  • 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS (tick)
  • 5000.2 IPV4: Add host intents between h1 and h9 - PASS (tick)

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

  • 18.1 Stopping and Removing Scapy Host Components - PASS (tick)
  • 18.2 Stopping Mininet - PASS (tick)

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

  • 19.1 Copying karaf logs - PASS (tick)