Versions Compared

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

commit 581c8407e613a27aaa573a600828b30a37066fb8 commit 0c484a7072f54189210033a4bc9d63d230c34618 (HEAD, origin/master, origin/HEAD, master)
Author: Ray Milkey pierventre [ray@opennetworkingpier@opennetworking.org]
AuthorDate: Wed Thu Sep 27 1723 19:25:45 2017 -070003:14 2021 +0200
Commit: Thomas Vachuska [tom@opennetworkingPier Luigi Ventre [pier@opennetworking.org]
CommitDate: Thu Mon Sep 28 1727 19:1027:33 2017 55 2021 +0000
Constructor is needed by the serializer

[SDFAB-616] Inconsistent format of port number in DhcpRelay
--
(cherry picked from commit 61bd673eec2282aff175daff141059870db78c7d)

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

...

  • 2.1 Apply cell to environment - PASS (tick)
  • 2.2 Uninstalling Atomix - PASS (tick)
  • 2.3 Uninstalling ONOS package - PASS (tick)
  • 2.3 4 Creating ONOS package - PASS (tick)
  • 2.5 Installing Atomix - PASS (tick)
  • 2.4 6 Installing ONOS package - PASS (tick)
  • 2.5 7 Set up ONOS secure SSH - PASS (tick)
  • 2.6 8 Checking ONOS service - PASS (tick)
  • 2.7 9 Starting ONOS CLI sessions - PASS (tick)
  • 2.10 Checking ONOS nodes - PASS (tick)
  • 2.11 Checking ONOS applications - PASS (tick)
  • 2.8 12 Checking that ONOS is ready - PASS (tick)
  • 2.9 13 setup the ipv6NeighbourDiscovery - PASS (tick)

...

  • 16.1 Balancing mastership of switches - PASS (tick)

Case 1000: Host Intents Test - 1 NODE(S) - OF 1.3 -

...

PASS

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

  • 1000.1 IPV6: Add host intents between h1 and h9 - FAIL (error)
  • IPV6: Host intent test failed between two IPV6 hosts
  • PASS (tick)
  • 1000.2 DUALSTACK1: Add host intents between h3 and h11 - FAIL (error)
    • DUALSTACK: Host intent test failed between twodual stack host using IPV6
  • 1000.3 1HOP: Add host intents between h1 and h3 - FAIL (error)
    • 1HOP: Host intent test failed between twohost using IPV6 in the same switch
  • 1000.4 VLAN: Add vlan host intents between h5 and h24 - FAIL (error)
  • VLAN1: Host intent test failed between twohost using IPV6 in the same VLAN
  • PASS (tick)
  • 1000.3 1HOP: Add host intents between h1 and h3 - PASS (tick)
  • 1000.4 VLAN: Add vlan host intents between h5 and h24 - PASS (tick)

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

This test case will test point to point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV6, 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, ipv6 hosts - PASS (tick)
  • 2000.2 IPV6: Add point intents between h1 and h9 - PASS (tick)
  • 2000.3 IPV6_2: Add point intents between h1 and h9 - PASS (tick)
  • 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS (tick)
  • 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 h24 - PASS (tick)
  • 2000.8 1HOP: Add point intents between h1 and h9 - PASS (tick)

Case 3000: Single to Multi Point Intents Test - 1 NODE(S) - OF 1.3 - PASS

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

  • 3000.1 NOOPTION: Add single point to multi point intents - PASS (tick)
  • 3000.2 IPV6: Add single point to multi point intents - PASS (tick)
  • 3000.3 IPV6_2: Add single point to multi point intents - PASS (tick)
  • 3000.4 VLAN: Add single point to multi point intents - PASS (tick)

Case 4000: Multi To Single Point Intents Test - 1 NODE(S) - OF 1.3 - FAIL

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

  • 4000.1 NOOPTION: Add multi point to single point intents - FAIL (error)
    • Assertion results for NOOPTION multi to single point intent
    • Initial Intent State Failed
    • Initial Flow Count Passed
    • Initial Flow State Passed
    • Initial Ping6all Passed
    • Link Down Passed
    • Link Down Topology State Passed
    • Link Down Ping6all Passed
    • Link Down Intent State Failed
    • Link Up Passed
    • Link Up Topology State Passed
    • Link Up Ping6all Passed
    • Link Up Intent State Failed
    • Remove Intents Failed
  • 4000.2 IPV6: Add multi point to single point intents - PASS (tick)
  • 4000.3 IPV6_2: Add multi point to single point intents - FAIL (error)
    • Assertion results for IPV6 multi to single point intent with IPV6 type and no MAC addresses
    • Initial Flow Count Passed
    • Initial Flow State Passed
    • Initial Ping6all Failed
    • Remove Intents Failed
  • 4000.4 VLAN: Add multi point to single point intents - FAIL (error)
    • Assertion results for IPV6 multi to single point intent with IPV6 type and no MAC addresses in the same VLAN
    • Initial Flow Count Passed
    • Initial Flow State Passed
    • Initial Ping6all Failed
    • Remove Intents Failed

Case 5000: Test host mobility with host intents - No Result