...
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 1a098eb4c351591084edfaae26cb394e4f950265 6155ff0df85d8909c0e4fbb281e4e8b44688f2b7 (HEAD -] master, origin/master, origin/HEAD)
Author: Harshada Chaundkar [harshada_chaundkar@comcast.comRay Milkey [ray@opennetworking.org]
AuthorDate: Tue Wed Jan 15 0023 16:0538:57 49 2019 +0000-0800
Commit: Charles Chan Ray Milkey [charles@opennetworkingray@opennetworking.org]
CommitDate: Tue Thu Jan 22 1824 00:4439:13 11 2019 +0000
PacketProcessorWebResource cannot find PacketService when it become instantiated; changed debug logs to trace in FPMManager
--
(cherry picked from commit 0d7cf74b85729c4346ae53b441793c24af0a3102)
Leave out private jars
Case 1: Pull onos branch and build onos on Teststation. - PASS
...
- 16.1 Balancing mastership of switches - PASS
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 - FAIL
- 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 Passed
- Link Up Flow State Passed
- Link Up Topology State Failed
- Link Up Pingall Passed
- Remove Intents Passed
- PASS
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
- 1000.6 Confirm that ONOS leadership is unchanged - PASS
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
- 2000.2 IPV4: Add point intents between h1 and h9 - PASS
- 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS
- 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 1000.2 DUALSTACK1: Add host intents between h3 and h11 - FAIL
- Assertion Result for dualstack IPV4 with MAC addressesSDNIP-ICMP IPV4 using TCP point intents
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping PassedFailed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State FailedPassed
- Link Down Topology State Passed
- Link Down Pingall PassedFailed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State FailedPassed
- Link Up Topology State Passed
- Link Up Pingall PassedScapy Packet Recieved Failed
- Remove Intents FailedPassed
- 1000.3 DUALSTACK2 2000.5 SDNIP-TCP: Add host point intents between h1 and h9 - PASS
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - FAIL
- Assertion Result for dualstack2 host intent
- Install Intent State Passed
- Flow duration check failed
- PASS
- 2000.7 VLAN: Add point intents between h5 and h21 - PASS
- 2000.8 1HOP: Add point 1000.4 1HOP: Add host intents between h1 and h3 - FAIL
- Assertion Result for 1HOP for IPV4 same switch
- Install Intent State Passed
- Flow duration check failed
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - FAIL
- Assertion Result vlan IPV4
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Pingall Passed
- Remove Intents Passed
- 1000.6 Confirm that ONOS leadership is unchanged - FAIL ONOS Leader Mismatch
- PASS
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 - PASS
- 3000.2 IPV4: Install and test single point to multi point intents - PASS
- 3000.3 IPV4_2: Add single point to multi point intents - PASS
- 3000.4 VLAN: Add single point to multi point intents - PASS
- 3000.5 VLAN: Add single point to multi point intents - PASS
Case 5000: Test host mobility with host intents - PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS
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
- 18.2 Stopping Mininet - PASS
Case 19: Copy karaf logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS