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

Missed nsm interface in the vL3 client's POD #7055

Closed
ThetaDR opened this issue Aug 10, 2022 · 4 comments · Fixed by networkservicemesh/sdk-vpp#635
Closed

Missed nsm interface in the vL3 client's POD #7055

ThetaDR opened this issue Aug 10, 2022 · 4 comments · Fixed by networkservicemesh/sdk-vpp#635
Assignees
Labels
bug Something isn't working
Milestone

Comments

@ThetaDR
Copy link
Contributor

ThetaDR commented Aug 10, 2022

Configuration with two clusters. Pod with redis does not have nsm interface even though that cmd-nsc container is running.
Cluster-info dumps are attached inside the archive.
cluster-info.zip

@denis-tingaikin denis-tingaikin changed the title No nsm interface in one of the pods Missed nsm interface in the vL3 client's POD Aug 10, 2022
@denis-tingaikin denis-tingaikin self-assigned this Aug 10, 2022
@denis-tingaikin denis-tingaikin added the bug Something isn't working label Aug 10, 2022
@denis-tingaikin denis-tingaikin added this to the v1.6.0 milestone Aug 10, 2022
@ThetaDR
Copy link
Contributor Author

ThetaDR commented Aug 16, 2022

The problem appeared one more time. Here's a new dump:
2-clusters-dump.zip

@ThetaDR
Copy link
Contributor Author

ThetaDR commented Aug 17, 2022

New dump:
cluster-1.txt.zip

@ThetaDR
Copy link
Contributor Author

ThetaDR commented Aug 17, 2022

dump-clusters.zip
Interface reappearing.

@ThetaDR
Copy link
Contributor Author

ThetaDR commented Aug 23, 2022

Steps for reproducing:

  1. setup interdomain.
  2. Setup vl3 (nse's NSM_REGISTER_SERVICE is set to true) .
  3. Start pods with nsm annotation on the first and second cluster.
  4. Delete the pod on the 2nd cluster. Then apply it once again.
    Sometimes it works just fine after one restart, so multiple restarts should show the bug

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

Successfully merging a pull request may close this issue.

3 participants