Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published from Jenkins build: https://onos-jenkins.onlab.us/job/FUNCintentRest/289/

...

  • 1000.1 IPV4: Add and test host intents between h1 and h9 - FAIL (error)
    • Assertion result for IPV4 host intent with mac addresses
    • 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 Failed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Pingall Passed
    • Remove Intents Passed
  • 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.2 DUALSTACK1: Add host intents between h3 and h11 - FAIL (error)
    • Assertion Result for dualstack IPV4 with MAC addresses
  • 1000.3 DUALSTACK2: Add host intents between h1 and h11 - FAIL (error)
    • Assertion Result for dualstack2 host intent
  • 1000.4 1HOP: Add host intents between h1 and h3 - PASS (tick)FAIL (error)
    • Assertion Result for 1HOP for IPV4 same switch
  • 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS (tick)FAIL (error)
    • Assertion Result vlan IPV4
  • 1000.6 VLAN2: Add inter vlan host intents between h13 and h20 - PASS (tick)FAIL (error)
    • Assertion Result different VLAN negative test
  • 1000.7 Confirm that ONOS leadership is unchanged - PASS (tick)FAIL (error)
    • ONOS Leader Mismatch

Case 2000: Point Intents Test - 3 NODE(S) - OF 1.3 -

...

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.3 OVS running in Mininet

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

Case 5000: Test host mobility with host intents -

...

FAIL

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

Case 17: Stop Mininet and Scapy -

...

FAIL

Stopping the current mininet topology to start up fresh

  • 17.1 Stopping and Removing Scapy Host Components - PASS (tick)
  • 17.2 Stopping Mininet Topology - PASS (tick)FAIL (error)
    • Failed to stop mininet