[VTN-128] CSIT for VTN Manager failed to verify ICMP action values in flowentries Created: 23/Mar/16 Updated: 19/Oct/17 Resolved: 18/Jul/16 |
|
| Status: | Resolved |
| Project: | vtn |
| Component/s: | VTN Manager |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Karthik Sivasamy | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
|
| External issue ID: | 5587 |
| Description |
|
The CSIT flow filter test case is failing in the verification of action ICMP code and type in flowentreis Order of Test scenarios execution Topology used Following are the steps followed in the CSIT test script for both OF10 and OF13. 1. Create Tenant1 In the above steps, Test cases failed in the below cases. For OF10: For OF13: To understand the above issues, analyzed karaf log for VTN Manager module while the above steps were executed. Flow entry were installed with ICMP values and removed only when remove flowfilter cases were excuted. But test fails only when verifying flows in mininet. For OF10: VBR Flow filter – Test steps 18 – 22 VBRIF Flow filter – Test steps 23 – 27 For OF13: VBR Flow filter – Test steps 18 – 22 VBRIF Flow filter – Test steps 23 – 27 Copied dumpflow output from Mininet in Sandbox: dump-flow log for OF10 in switch s3: Here we can see ICMP code and type value set as actions=mod_tp_dst:1,mod_tp_src:3
dump-flow log for OF13 in switch s3: Here ICMP code and type values are not set in flowentries.
Attached karaf log file as icmp_karaf.zip |
| Comments |
| Comment by Karthik Sivasamy [ 23/Mar/16 ] |
|
Attachment icmp_karaf.zip has been added with description: Karaf log enabled TRACE for VTN Manager |
| Comment by Karthik Sivasamy [ 14/Jul/16 ] |
|
Steps followed for verifying the Bug: Tested with Be/SR2 distro for verification of action ICMP code and type in flowentries. Since ICMP code and type are not supported in ovs2.3.0 Issue is not reproduced. Now i can see in flowentries created with ICMP code and type actions successfully. Verified both Karaf.log and mininet, i have seen icmp parameters. Followed the same steps which i followed when i raised the bug, which is in the earlier commetns. Mininet Output:
Karaf Log: 2016-07-14 08:29:34,422 | DEBUG | TN Flow Thread-0 | FlowAddContext | 189 - org.opendaylight.vtn.manager.implementation - 0.4.2.Beryllium-SR2 | Data flow has been installed: id=9 , actions= {OUTPUT(port=openflow:1:2, len=65535)}2016-07-14 08:29:34,432 | TRACE | TN Flow Thread-0 | FlowAddContext | 189 - org.opendaylight.vtn.manager.implementation - 0.4.2.Beryllium-SR2 | Flow entry has been installed: flow=[id=7f5600000000000a-2, pri=14, timeout=(0,0), node=openflow:3, ingress=openflow:3:3, cond= {DL_SRC=ea:a1:b9:df:06:6e,DL_DST=9e:89:4a:13:cc:80,DL_TYPE=2048,DL_VLAN=0,IP_SRC=10.0.0.1,IP_DST=10.0.0.3,IP_PROTO=1}, actions= {SET_TP_DST(port=3), SET_TP_SRC(port=6), OUTPUT(port=openflow:3:1, len=65535)}2016-07-14 08:29:34,436 | TRACE | TN Flow Thread-0 | FlowAddContext | 189 - org.opendaylight.vtn.manager.implementation - 0.4.2.Beryllium-SR2 | Flow entry has been installed: flow=[id=7f5600000000000a-0, pri=14, timeout=(300,0), node=openflow:2, ingress=openflow:2:1, cond= {DL_SRC=ea:a1:b9:df:06:6e,DL_DST=9e:89:4a:13:cc:80,DL_TYPE=2048,DL_VLAN=0,IP_SRC=10.0.0.1,IP_DST=10.0.0.3,IP_PROTO=1}, actions= {OUTPUT(port=openflow:2:3, len=65535)}2016-07-14 08:29:34,436 | DEBUG | TN Flow Thread-0 | FlowAddContext | 189 - org.opendaylight.vtn.manager.implementation - 0.4.2.Beryllium-SR2 | Data flow has been installed: id=10 Below are the flowentries from mininet for OF10. 1. Create Tenant1 |
| Comment by Karthik Sivasamy [ 14/Jul/16 ] |
|
I have Tested for below keytypes, • VTN Flow filter And in mininet i have created topolofy in both OF10 and OF13 switch. Both are working fine. |
| Comment by Karthik Sivasamy [ 14/Jul/16 ] |
|
Tested manually to verify ICMP code and Type action in Flowentries, by updating OVS version from 2.3.1 to 2.5.0 and found issue is not reproduced. So updated status to Resolved and "Wontfix" Since CSIT cases not yet fixed, in releng CSIT environment, OVS version not yet updated to OVS 2.5.0. Changing of actions ICMP code and types fields are supported from OVS 2.5.0. Once the OVS version is updated to OVS2.5.0 in releng environment, we will apply fix the patch to enable ICMP code and Type cases. And then we will change bug status to 'Resolved' and 'Fixed'. |