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

Bug with nse-composition example. #11929

Open
isZams opened this issue May 9, 2024 · 1 comment
Open

Bug with nse-composition example. #11929

isZams opened this issue May 9, 2024 · 1 comment

Comments

@isZams
Copy link

isZams commented May 9, 2024

Expected Behavior

Hi everyone.
I'm trying to use the nse-composition, modified to handle kernel interfaces in the composition. However, using a cluster with a single node, everything is ok. Using a cluster with 2 worker nodes and 1 master, the pod in the middle of the chain (composed by 3 elements) cannot start.
Here there are:

  • folder example-composition.zip to deploy the K8s resources
  • logs file logs.txt about the error of the pod in the middle of the chain.
    The logs underline how is missing the config.yaml that is used by the PBR example. However i didn't configure this example to handle also this part and in the other case this error does not appear.

Thanks for your help in advance!

EDIT

I was checking where the various pods were located in the nodes. Could there be a problem with pods, even of the same namespace, being located on different nodes?

suricata             nse-kernel-86db86bcd5-zbdhr                 2/2     Running            3 (60m ago)      17h   10.244.1.4   nsm-worker2         <none>           <none>
suricata             nse-passthrough-4-5868687d95-2zmnj          2/3     CrashLoopBackOff   25 (2m44s ago)   17h   10.244.2.4   nsm-worker          <none>           <none> 
@isZams
Copy link
Author

isZams commented May 10, 2024

I deployed the pods within the same node but the problem is still there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant