[OPNFLWPLUG-193] of-flow: instruction/clear-actions details missing in operational data store Created: 12/Jun/14 Updated: 27/Sep/21 Resolved: 21/Jun/14 |
|
| Status: | Resolved |
| Project: | OpenFlowPlugin |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Peter Gubka | Assignee: | Anil Vishnoi |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Linux |
||
| Attachments: |
|
| External issue ID: | 1192 |
| Description |
|
odl: test: mininet 2.1.0 + ovs 2.0.0 steps: 2) GET its operational state (for full details see f219odb.xml in attachment) 4) seen difference operational: Tag <clear-actions/> is empty |
| Comments |
| Comment by Peter Gubka [ 12/Jun/14 ] |
|
Attachment f219.xml has been added with description: flow to be configured |
| Comment by Peter Gubka [ 12/Jun/14 ] |
|
Attachment f219odb.xml has been added with description: operational details of the flow |
| Comment by Anil Vishnoi [ 21/Jun/14 ] |
|
Hi Peter, I am able to recreate this bug in my setup, but i think this bug goes to the same category as mininet> sh ovs-ofctl dump-flows s1 -O OpenFlow13 So if you see clear_actions don't have any sub actions and this behavior is correct as per specs as well. This is what specs says So stats reported in operation data store is correct, but i believe issue mainly is what we install and what finally get installed on the switch. As we discussed previously it needs some level of sanity check at plugin level. Thanks |