Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

race condition between vpp api connect and vpp init links during startup #649

Open
zolug opened this issue Jun 2, 2022 · 0 comments
Open
Labels
bug Something isn't working

Comments

@zolug
Copy link
Contributor

zolug commented Jun 2, 2022

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

@zolug zolug added the bug Something isn't working label Jun 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant