[SFC-213] SFC RSP statistics are not working in Oxygen RC0 release Created: 27/Feb/18 Updated: 08/Mar/18 Resolved: 08/Mar/18 |
|
| Status: | Verified |
| Project: | sfc |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | Oxygen |
| Type: | Bug | Priority: | High |
| Reporter: | Brady Johnson | Assignee: | Brady Johnson |
| Resolution: | Done | Votes: | 0 |
| Labels: | patch_merged | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
If the OVS bridge to be used for the SFF has not already been created, then the SFC RSP statistics dont work. This is due to a race condition when SFC creates the ovs bridge and simultaneously trying to access the bridge OpenFlow DPID. |
| Comments |
| Comment by Brady Johnson [ 27/Feb/18 ] |
|
There are 2 scenarios to be taken into account:
If the ovs bridge already exists when the SFF is created, then the OpenFlow NodeId is correctly added to the SFF by SfcOvsSffEntryDataListener. But this listener does not handle case 2 above, since it creates the ovs bridge in the configuration data store (as it should) and the OpenFlow ID is added to the operational ovs bridge data, which isnt available during the scope of this listener. If the ovs bridge is created when the SFF is created or even later if the ovs manager isnt connected to ODL yet, then the OpenFlow NodeId will be added to the SFF by SfcOvsNodeDataListener when the ovs bridge is created, thus handling case 2 above.
|
| Comment by Brady Johnson [ 27/Feb/18 ] |
|
This has been fixed in stable/oxygen with this patch: https://git.opendaylight.org/gerrit/#/c/68841/
|
| Comment by Daniel Farrell [ 07/Mar/18 ] |
|
ebrjohn Can you confirm this is fixed and close the bug? |