You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
socketID=atomic.AddUint32(&lastSocketID, 1) // TODO - work out a solution that works long term
It is totally incorrect for the single VPP scenario (e.g. with Calico VPP) - Client, Forwarder and Endpoint start requesting VPP with the same socket IDs and fail.
Bolodya1997
changed the title
memif socket ID generation is wrong for the single VPP scenario
[Calico/VPP NSM integration] memif socket ID generation is wrong for the single VPP scenario
Sep 2, 2021
Issue
Currently
memif
generates socket IDs incrementing some per-application counter:sdk-vpp/pkg/networkservice/mechanisms/memif/common.go
Line 54 in 914e91e
It is totally incorrect for the single VPP scenario (e.g. with Calico VPP) - Client, Forwarder and Endpoint start requesting VPP with the same socket IDs and fail.
Parent issue
networkservicemesh/integration-k8s-kind#325
Possible solution
Use some random generator for creating socket IDs + check for "already exists" error to retry:
The text was updated successfully, but these errors were encountered: