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

...

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 25669c6ddf72a22d3d2cfa091298012a7386001a f519e3d061e21b84c61fe478969fa9dc55578810 (HEAD -] master, origin/master, origin/HEAD)
Author: Seyeon Jeong Jonathan Hart [seyeon@opennetworkingjono@opennetworking.org]
AuthorDate: Wed Feb 19 17:51:05 Tue Jan 28 14:10:47 2020 -0800
Commit: Charles Chan Jonathan Hart [charles@opennetworkingjono@opennetworking.org]
CommitDate: Fri Tue Feb 21 0125 19:4228:24 56 2020 +0000
Fix possible NPE when 't3-troubleshoot-pingall' command on a host without IP addr
--
(cherry picked from commit 980eea4a63639bf082570c8bf9e882554921112a)
Add MetadataInstruction to the API serializer namespace

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

...

  • 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
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Bad Sender Ping Passed
    • Bad Recipient Ping Passed
    • 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
  • 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

...

  • 16.1 Balancing mastership of switches - PASS (tick)

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

...

FAIL

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 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 - 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)FAIL (error)
    • Assertion Result vlan IPV4
    • Install Intent State Passed
    • Flow duration check failed
  • 1000.6 Confirm that ONOS leadership is unchanged - PASS (tick)FAIL (error)
    • ONOS Leader Mismatch

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

...