Closed chrispsommers closed 3 years ago
Hi @chrispsommers, thanks for the issue report! It looks like for your example case there are multiple updates in a single gNMI notification and gnmi-gateway wasn't correctly handling errors for multiple updates. I made a fix for the error handling process but after reading through your issue a second time I'm not sure that my fix actually covers your concern regarding the expected behavior:
Receive notifications without error messages, expose to northbound.
My change will allow notifications to be received and the connection to be stable but won't do anything else besides continuing to drop stale updates (i.e. won't forward stale updates to clients or Exporters). This is actually a function of the cache from the gnmi library and not something the gateway has direct control over without making multiple copies of the notifications.
Can you clarify what details you expect to be exposed when a stale update is received? Or if the fix I'm going to merge in covers your concerns feel free to close out the issue too.
I'm going to close this issue. Feel free to re-open this or comment if the merged commits link above don't resolve your issue.
Bug description Get "cache update error: update is stale," error after receiving subscription notification from a target.
Step to reproduce
Expected behavior Receive notifications without error messages, expose to northbound.
gnmi-gateway logs:
Target logs (partial) showing notifications being sent to server:
Environment details
Additional context I'm able to subscribe to this client using gnmi_cli, see below. Note this version is patched to support some of the options below, not sure it matters).
Patch inside gnmi_cli source dir:
Subscribe result: