[VTN-166] vtn-inet-match protocol and dscp values not mapped from VTN Coordinator to VTN manager

Mon, 30 Oct 2017 15:20:45 +0000

Issue Scenario :

The dscp,protocol values from the Coordinator flowlistentry are not mapped in the VTN Manager

Reproduce the Bug:

set-up for vtn manager and coordinator using the example:
Create Flowlistentries as shown on the below page:

In the flowlistentry command give the ipdscp,protocol attributes as given below:

curl -v --user admin:adminpass -H 'content-type: application/json' -X POST -d '{"flowlistentry": {"seqnum": "1","dscp": "23", "ipproto": "6"}}' http://127.0.0.1:8083/vtn-webapi/flowlists/flowlist1/flowlistentries.json

The Request body in the Coordinator logs :

http://10.106.138.150:8181/restconf/operations/vtn-flow-condition:set-flow-condition-match Url formed
2017-09-27 20:51:11.107059: [7123]: DEBUG: restjsonutil: HTTP_METHOD_POST
2017-09-27 20:51:11.107071: [7123]: DEBUG: restjsonutil: Request Body : { "input": { "name": "flowlist1", "flow-match-list": [

{ "index": 1 }

] } }
2017-09-27 20:51:11.107079: [7123]: INFO: restjsonutil: requestbody : { "input": { "name": "flowlist1", "flow-match-list": [

{ "index": 1 }

] } }

The below mentioned is from the VTN Manager obtained by GET command :

{"vtn-flow-condition":[{"name":"flowlist1","vtn-flow-match":[

{"index":1}

]}]}

The below mentioned is from the VTN Coordinator obtained by GET command :

{"flowlistentry":{"ipdscp":"23","seqnum":"1","ipproto":"6"}}

THE IPDSCP and IPPROTO Values are present in VTN Coordinator but not mapped to VTN manager.

Occurrence of the issue :

Occurs every time during creation of flowlistentries with the ipdscp,protocol attributes

OpenDaylight JIRA