The ovs bridge already exists when the SFF is created.
The ovs bridge does not exist when the SFF is created, and the bridge is created when the SFF is created.
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.
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.