[VTN-62] Wrong mapping of flow-list entry attributes (ipdscp, protocol, icmptype, icmpcode) from VTN Coordinator to VTN manager. Created: 23/Mar/15 Updated: 19/Oct/17 Resolved: 07/Jul/15 |
|
| Status: | Resolved |
| Project: | vtn |
| Component/s: | ODC Driver |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | YOGA LAKSHMI SWETHA PAYYAVULA | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 2887 |
| Description |
|
Issue Scenario : The dscp,protocol,icmp type,icmp code values from the Coordinator flowlistentry are wrongly mapped in the VTN Manager Reproduce the Bug: First get a set-up for vtn manager and coordinator using the example: In the flowlistentry command give the ipdscp,protocol,icmptype and icmpcode attributes as given below: curl -v --user admin:adminpass -H 'content-type: application/json' -X POST -d '{"flowlistentry": {"seqnum": "233","macethertype": "0x800","ipdstaddr": "10.0.0.1","ipdstaddrprefix": "32","ipsrcaddr": "10.0.0.3","ipsrcaddrprefix": "32","dscp": "17", "ipproto": "1", "icmptypenum": "200", "icmpcodenum": "10" }}' http://127.0.0.1:8083/vtn-webapi/flowlists/flowlist1/flowlistentries.json The Request body in the Coordinator logs : 2015-03-18 23:43:12.817474: [12796]: INFO: restjsonutil: requestbody : : { "index": 233, "ethernet": { "type": 2048 }, "inetMatch": { "inet4": { "protocol": 17, "src": "10.0.0.3", "dst": "10.0.0.1" }}, "l4Match": { "icmp": { "type": 10 }} } The below mentioned is from the VTN Manager obtained by GET command : {"name":"flowlist1","match":[{"ethernet": {"type":2048},"inetMatch":{"inet4":{"protocol":17,"src":"10.0.0.3","dst":"10.0.0.1"}},"l4Match":{"icmp":{"type":10}},"index":233}]} THE IPDSCP and ICMP CODE Values are mismatched with IPPROTOCOL and ICMP TYPE in the VTN Manager Occurrence of the issue : Occurs every time during creation of flowlistentries with the ipdscp,protocol,icmptype,icmpcode attributes |
| Comments |
| Comment by YOGA LAKSHMI SWETHA PAYYAVULA [ 27/Mar/15 ] |
|
Due to this issue looping occurs in the controller,when the flowfilter is created. |
| Comment by Hideyuki Tai [ 27/Mar/15 ] |
|
(In reply to YOGA LAKSHMI SWETHA PAYYAVULA from comment #1) Could you add more explanation about "looping"? |
| Comment by YOGA LAKSHMI SWETHA PAYYAVULA [ 30/Mar/15 ] |
|
When the flowfitler is created with wrong flowlistentry attribute values,there is a REST API failure, that results in VTN Coordiantor triggering repeated AUDITS to fix the issue, which is causes looping.The logs for the same is shown below : -24 01:22:19.911 IST [http-bio-8080-exec-7] INFO o.o.v.m.i.cluster.FlowFilterMap - default:vBridge-IF:vtn1.vbr1.if1:IN.233: Flow filter was added. |
| Comment by YOGA LAKSHMI SWETHA PAYYAVULA [ 04/May/15 ] |
|
The patch for this bug was merged into the master branch of the vtn.git : https://git.opendaylight.org/gerrit/17110 The patch for this was also merged in the stable/helium branch of the vtn.git: |