[CONTROLLER-107] Flows programmed in Tables other than Table 0 do not show in the operational data for their respective table. Created: 28/Dec/13  Updated: 25/Jul/23  Resolved: 05/May/15

Status: Resolved
Project: controller
Component/s: adsal
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Jan Medved Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Mac OS
Platform: Macintosh


External issue ID: 264

 Description   

When issuing a request to get operational data for a Table, flows in that Table should be shown through RESTCONF. For example, getting operational data for Table 1 should show the active flows in Table 1: issuing GET to 'http://192.168.4.1:8080/restconf/operational/opendaylight-inventory:nodes/node/openflow:1/table/2' should get the statistics and flows for Table 2. Only the statistics are shown:

{
"flow-node-inventory:table": [
{
"flow-node-inventory:id": 2,
"opendaylight-flow-table-statistics:flow-table-statistics":

{ "opendaylight-flow-table-statistics:packets-looked-up": 0, "opendaylight-flow-table-statistics:packets-matched": 0, "opendaylight-flow-table-statistics:active-flows": 1 }

}
]
}

No flow data is shown, altough there are active flows, as can be seen above.

This is true for all tables, except for Table 0, where the first programmed flow is shown



 Comments   
Comment by Jan Medved [ 12/Jan/14 ]

Not an issue

Comment by Carol Sanders [ 05/May/15 ]

This bug is part of the project to Move all ADSAL associated component bugs to ADSAL.

Generated at Wed Feb 07 19:52:12 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.