[OPNFLWPLUG-922] Inconsistency between flows in config, operational, and the OVS bridge Created: 11/Jul/17  Updated: 27/Sep/21  Resolved: 17/Jul/17

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

Type: Bug
Reporter: Brady Johnson Assignee: Brady Johnson
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: 8836

 Description   

It looks like something has changed in the OpenflowPlugin in the Carbon release. I remember in previous projects, when a flow is created you could query it in the config data store. And then when the flow gets installed in an OVS bridge, you could query the same flow in the operational data store.

I tried doing this with Carbon and Nitrogen and am observing a different behavior. I can see the flows in the config data store just fine. The flows also get installed in the OVS bridge as expected, but several of the flows are not in the operational data store, and those that are there are incomplete.

Here's an example of what Im talking about for SFC table=4 flows using Carbon, although I see the same behavior with Nitrogen:

Config Flows in table=4:
(Notice there are 3 flows)
https://pastebin.com/CzCkae3a

Operational flows in table=4:
(Notice there are 2 flows)
https://pastebin.com/1YezfFQ3

And here are the flows in the OVS bridge in table=4:
(Notice there are 3 flows)
https://pastebin.com/uj74f9TR

The flows in the OVS bridge match what are in the config data store. There are only 2 flows in the oper data store instead of the expected 3, and one of these has an incomplete match.

Regards,

Brady



 Comments   
Comment by Tomas Slusny [ 12/Jul/17 ]

Gerrit patches:
master: https://git.opendaylight.org/gerrit/#/c/60243/
stable/carbon: https://git.opendaylight.org/gerrit/#/c/60245/

Comment by Tomas Slusny [ 17/Jul/17 ]

Both patches was merged, tested this in my local environment and it resolved issue. Marking this bug as resolved.

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