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

NSM Connection fails if spire-agent restarts on NSC node #2393

Closed
Bolodya1997 opened this issue Aug 2, 2021 · 2 comments · Fixed by networkservicemesh/sdk#1069
Closed

NSM Connection fails if spire-agent restarts on NSC node #2393

Bolodya1997 opened this issue Aug 2, 2021 · 2 comments · Fixed by networkservicemesh/sdk#1069
Assignees
Labels
bug Something isn't working stability The problem is related to system stability

Comments

@Bolodya1997
Copy link

Bolodya1997 commented Aug 2, 2021

Expected Behavior

NSM connection shouldn't fail is spire-agent dies for some little time, or should be eventually restored if it dies for a long time.

Current Behavior

NSM connection fails if spire-agent restart on NSC node:

  1. Refresh Request from NSC to NSMgr fails (NSC -> NSE network connection still exists).
  2. Healing from NSC to NSMgr fails (NSC -> NSE network connection fails).

Steps to Reproduce

  1. Run kernel2kernel test case, check that ping is working.
  2. Restart spire-agent pod on the NSC node.
  3. Wait for the token timeout.
  4. Ping is not working.

Failure Logs

nsc-kernel-7cb47459d5-g9j6c.log
nsmgr-qq66h.log
forwarder-vpp-hgttp.log
nse-kernel-79ffb869cc-796fc.log

@Bolodya1997 Bolodya1997 added the bug Something isn't working label Aug 2, 2021
@Bolodya1997
Copy link
Author

Seems to be related to #1929.

@Bolodya1997 Bolodya1997 self-assigned this Aug 6, 2021
@denis-tingaikin
Copy link
Member

Don't quite follow how it is related to #1929. Could you say more?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stability The problem is related to system stability
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants