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
In startup phase 2 (run vpp and get a connection to it) forwarder-vpp does not wait for the VPP conn to get ready before moving on to subsequent phases. Thus vppinit.InitLinks might fail thus basically rendering the forwarder non functional.
VPP is not running on the host when starting the forwarder.
The problem seems to occur sporadically.
A DeviceSelectorFile is used containing around 7-8 interface entries.
In vpphelper.StartAndDialContext() func DialContext() returns with the connection while the connect might be still in progress.
However, the ready channel is not checked by the forwarder (the Connection interface doesn't seem to provide any means for that). Also, error returned by vppinit.InitLinks() is not considered fatal.
NSM version: v1.4.0-rc.1
k8s: v1.22.2
The text was updated successfully, but these errors were encountered:
In startup phase 2 (run vpp and get a connection to it) forwarder-vpp does not wait for the VPP conn to get ready before moving on to subsequent phases. Thus vppinit.InitLinks might fail thus basically rendering the forwarder non functional.
VPP is not running on the host when starting the forwarder.
The problem seems to occur sporadically.
A DeviceSelectorFile is used containing around 7-8 interface entries.
In vpphelper.StartAndDialContext() func DialContext() returns with the connection while the connect might be still in progress.
However, the ready channel is not checked by the forwarder (the Connection interface doesn't seem to provide any means for that). Also, error returned by vppinit.InitLinks() is not considered fatal.
NSM version: v1.4.0-rc.1
k8s: v1.22.2
The text was updated successfully, but these errors were encountered: