[OPNFLWPLUG-747] Modified flow does not reconcile in configuration (show alien ID) Created: 18/Aug/16  Updated: 27/Sep/21  Resolved: 19/Aug/16

Status: Resolved
Project: OpenFlowPlugin
Component/s: General
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Luis Gomez Assignee: Shuva Jyoti Kar
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 6458

 Description   

This tracked here:

https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-flow-services-only-boron/

To reproduce:

1) Add a flow to a switch:

{
"flow-node-inventory:flow": [
{
"id": "1",
"priority": 2,
"flow-name": "flow1",
"table_id": 0,
"idle-timeout": 0,
"hard-timeout": 0,
"instructions": {
"instruction": [
{
"order": 0,
"apply-actions": {
"action": [
{
"order": 0,
"output-action":

{ "output-node-connector": "1" }

}
]
}
}
]
},
"match": {
"ipv4-destination": "10.0.10.0/24",
"ethernet-match": {
"ethernet-type":

{ "type": 2048 }

}
}
}
]
}

2) Check flow is in operational with id=1

3) Modify flow (change IP match):

{
"flow-node-inventory:flow": [
{
"id": "1",
"priority": 2,
"flow-name": "flow1",
"table_id": 0,
"idle-timeout": 0,
"hard-timeout": 0,
"instructions": {
"instruction": [
{
"order": 0,
"apply-actions": {
"action": [
{
"order": 0,
"output-action":

{ "output-node-connector": "1" }

}
]
}
}
]
},
"match": {
"ipv4-destination": "10.0.20.0/24",
"ethernet-match": {
"ethernet-type":

{ "type": 2048 }

}
}
}
]
}

4) Flow shows alien ID in operational.

{
"flow-node-inventory:table": [
{
"id": 0,
"flow": [
{
"id": "#UF$TABLE*0-2",
"opendaylight-flow-statistics:flow-statistics": {
"packet-count": 0,
"duration":

{ "nanosecond": 112000000, "second": 39 }

,
"byte-count": 0
},
"priority": 2,
"table_id": 0,
"hard-timeout": 0,
"match": {
"ethernet-match": {
"ethernet-type":

{ "type": 2048 }

},
"ipv4-destination": "10.0.20.0/24"
},
"cookie": 0,
"flags": "",
"instructions": {
"instruction": [
{
"order": 0,
"apply-actions": {
"action": [
{
"order": 0,
"output-action":

{ "max-length": 0, "output-node-connector": "1" }

}
]
}
}
]
},
"idle-timeout": 0
}
],
"opendaylight-flow-table-statistics:flow-table-statistics":

{ "packets-matched": 12594, "active-flows": 1, "packets-looked-up": 12855 }

}
]
}

 Comments   
Comment by Jozef Bacigal [ 18/Aug/16 ]

This is all the strange thing with TWO flows with the SAME ID. We should never allowed this. We should take back all this nonsense, because we are getting deeper into problems ...

Comment by Shuva Jyoti Kar [ 18/Aug/16 ]

(In reply to Jozef Bacigal from comment #1)
> This is all the strange thing with TWO flows with the SAME ID. We should
> never allowed this. We should take back all this nonsense, because we are
> getting deeper into problems ...

Actually i still feel we need to keep the flowregistrykey--> flowDescriptor pair unique since the flowid is the one we need, to put the flow in the confg datastore. The issue here is the updated callback doesnot remove the already existing entry. Will push in a patch for the same, that should take care.

Comment by Shuva Jyoti Kar [ 19/Aug/16 ]

https://git.opendaylight.org/gerrit/#/c/44281/

https://git.opendaylight.org/gerrit/#/c/44244/

Generated at Wed Feb 07 20:33:17 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.