generated from networkservicemesh/cmd-template
-
Notifications
You must be signed in to change notification settings - Fork 21
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
VPP sometimes crashed on signal (SIGILL, SIGSEGV) #881
Comments
Another example, crashed on Fragment
|
nsmbot
pushed a commit
that referenced
this issue
Feb 20, 2025
…k-vpp@main PR link: networkservicemesh/sdk-vpp#881 Commit: e4c654e Author: Network Service Mesh Bot Date: 2025-02-20 06:39:20 -0600 Message: - Update go.mod and go.sum to latest version from networkservicemesh/sdk-kernel@main (#881) PR link: networkservicemesh/sdk-kernel#707 Commit: fb5f776 Author: Network Service Mesh Bot Date: 2025-02-20 06:35:31 -0600 Message: - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#707) PR link: networkservicemesh/sdk#1709 Commit: acd16f3 Author: dependabot[bot] Date: 2025-02-20 13:33:13 +0100 Message: - Bump golang.org/x/crypto from 0.21.0 to 0.31.0 (#1709) Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.21.0 to 0.31.0. - [Commits](golang/crypto@v0.21.0...v0.31.0) --- updated-dependencies: - dependency-name: golang.org/x/crypto dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When running tests I sometimes see that forwarder is restarted, and the previous container stopped working after vpp binary got killed via SIGILL signal.
I got it several times in
TestRunHealSuite/TestVl3_nscs_death
test.It seems like there is something wrong with IPSEC mechanism.
Logs
Fragment
TestRunHealSuite.zip
The text was updated successfully, but these errors were encountered: