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/1304/

...

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 655b9a885fd063ee5aea2a3bbd4c2b62b69943de da3b9f09807e4054835495b1d61b3956ef5c5cbd (HEAD -] master, origin/master, origin/HEAD)
Author: jayakumarthazhath Jordan Halterman [jayakumarjordan@opennetworking.thazhath@infosys.comorg]
AuthorDate: Mon Oct 1 00Fri Oct 5 13:28:51 :54 2018 +0530-0700
Commit: Charles Chan [rascov@gmailcharles@opennetworking.comorg]
CommitDate: Thu Tue Oct 4 119 17:1124:19 2018 -0700
Prevent XConnect loop35 2018 +0000

Avoid closing DeviceFlowTable when flows are purged on device down event
--
(cherry picked from commit cd4276521ca0a7268353317ede37de33cdbe4c52)

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

...

  • 16.1 Balancing mastership of switches - PASS (tick)

Case 1000: Host Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Rules -

...

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.0 OVS running in Mininet and compile intents using Flow Rules

  • 1000.1 IPV4: Add and test host intents between h1 and h9 - 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 DUALSTACK2: Add host intents between h1 and h11 - PASS (tick)
  • 1000.4 1HOP: Add host intents between h1 and h3 - PASS (tick)
  • 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS (tick)
  • 1000.6 Confirm that ONOS leadership is unchanged - PASS (tick)

Case 2000: Point Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Rules -

...

FAIL

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.0 OVS running in Mininet and compile intents using Flow Rules

  • 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS (tick)
  • 2000.2 IPV4: Add point intents between h1 and h9 - PASS (tick)
  • 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS (tick)
  • 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS (tick)FAIL (error)
    • Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Failed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved Failed
    • Remove Intents Passed
  • 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - 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.0 - Using Flow Rules -

...

PASS

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.0 OVS running in Mininet and compile intents using Flow Rules

  • 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
  • PASS (tick)
  • 3000.2 IPV4: Install and test single point to multi point intents - PASS (tick)
  • 3000.3 IPV4_2: Add single point to multi point intents - PASS (tick)
  • 3000.4 VLAN: Add single point to multi point intents - PASS (tick)
  • 3000.5 VLAN: Add single point to multi point intents - PASS (tick)

...

  • 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 Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Failed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Pingall Passed
    • addresses
    • Install Intent State Remove Intents Failed
  • 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 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
  • 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.0 - Using Flow Objectives - FAIL

...

  • 2000.1 NOOPTION: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for NOOPTION point intent
    • Install Intent State Failed
  • PASS (tick)
  • 2000.2 IPV4: Add point intents between h1 and h9 - PASS (tick)
  • 2000.3 IPV4_2 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_24 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for IPV4 no mac address SDNIP-ICMP IPV4 using TCP point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
  • 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL (error)
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Failed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved Failed
    • Remove Intents Passed
    • Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
    • Install Intent State Failed
  • 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for SDNIP-TCP IPV4 using ICMP point intents
  • PASS (tick)
  • 2000.6 DUALSTACK1: Add point intents between h3 and h11 - FAIL (error)
    • Assertion Result for Dualstack1 IPV4 with mac address point intents
    • Install Intent State Failed
  • 2000.7 VLAN: Add point intents between h5 and h21 - FAIL (error)
    • Assertion Result for VLAN IPV4 with mac address point intents
    • Install Intent State Failed
  • 2000.8 1HOP: Add point intents between h1 and h3 - FAIL (error)
    • Assertion Result for 1HOP IPV4 with no mac address point intents
    • Install Intent State Failed

...

  • 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
  • PASS (tick)
  • 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
  • point intents - PASS (tick)
  • 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
  • PASS (tick)
  • 3000.5 VLAN: Add single point to multi point intents - FAIL (error)
  • Assertion results for single to multi point intent with VLAN treatment
  • PASS (tick)

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 - FAIL (error)
    • Assert result for IPV4 host intent between h1, moved, and h9
    • Install Intent State Failed
  • PASS (tick)

Case 18: Stop Mininet and Scapy - PASS

...

  • 3000.1 NOOPTION: Install and test single point to multi point intents - PASS (tick)
  • 3000.2 IPV4: Install and test single point to multi point intents - PASS (tick)
  • 3000.3 IPV4_2: Add single point to multi point intents - PASS (tick)
  • 3000.4 VLAN: Add single point to multi point intents - PASS (tick)
  • 3000.5 VLAN: Add single point to multi point intents - PASS (tick)

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)

...

  • 3000.1 NOOPTION: Install and test single point to multi point intents - PASS (tick)
  • 3000.2 IPV4: Install and test single point to multi point intents - PASS (tick)
  • 3000.3 IPV4_2: Add single point to multi point intents - PASS (tick)
  • 3000.4 VLAN: Add single point to multi point intents - PASS (tick)
  • 3000.5 VLAN: Add single point to multi point intents - PASS (tick)

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)

...

  • 3000.1 NOOPTION: Install and test single point to multi point intents - PASS (tick)
  • 3000.2 IPV4: Install and test single point to multi point intents - PASS (tick)
  • 3000.3 IPV4_2: Add single point to multi point intents - PASS (tick)
  • 3000.4 VLAN: Add single point to multi point intents - PASS (tick)
  • 3000.5 VLAN: Add single point to multi point intents - PASS (tick)

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)

...

  • 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 Passed
  • Flow duration check 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 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 - FAIL

...

  • 2000.1 NOOPTION: Add point intents between h1 and h9 - FAIL (error)
  • Assertion Result for NOOPTION point intent
  • Install Intent State Failed
  • PASS (tick)
  • 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 - PASS (tick)
  • 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for IPV4 no mac address point intents
    • Install Intent State Failed
  • 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL (error)
    • SDNIP-ICMP IPV4 using TCP point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Failed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved Failed
    • Remove Intents Passed
    • Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
    • Install Intent State Failed
  • 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for SDNIP-TCP IPV4 using ICMP point intents
  • 2000.6 DUALSTACK1: Add point intents between h3 and h11 - FAIL (error)
  • Assertion Result for Dualstack1 IPV4 with mac address point intents
  • PASS (tick)
  • 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)
  • Install Intent State Failed
  • 2000.7 VLAN: Add point intents between h5 and h21 - FAIL (error)
  • Assertion Result for VLAN IPV4 with mac address point intents
  • Install Intent State Failed
  • PASS (tick)
  • 2000.8 1HOP: Add point intents between h1 and h3 - FAIL (error)
    • Assertion Result for 1HOP IPV4 with no mac address point intents
    • Install Intent State Failed
  • PASS (tick)

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

...

PASS

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
  • PASS (tick)
  • 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
  • intents - PASS (tick)
  • 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
  • PASS (tick)
  • 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
  • PASS (tick)
  • 3000.5 VLAN: Add single point to multi point intents - FAIL (error)
  • Assertion results for single to multi point intent with VLAN treatment
  • PASS (tick)

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 - FAIL (error)
  • Assert result for IPV4 host intent between h1, moved, and h9
  • Install Intent State Failed
  • PASS (tick)

Case 18: Stop Mininet and Scapy - PASS

...