-
Notifications
You must be signed in to change notification settings - Fork 17
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
Missing policy routes #685
Comments
ljkiraly
added a commit
to Nordix/nsm-sdk-kernel
that referenced
this issue
Oct 28, 2024
Issue: networkservicemesh#685 Try to delete the rule even if the route deletion fails. For example when the belonging interface is deleted in parallel.
ljkiraly
added a commit
to Nordix/nsm-sdk-kernel
that referenced
this issue
Oct 28, 2024
Issue: networkservicemesh#685 Try to delete the rule even if the route deletion fails. For example when the belonging interface is deleted in parallel. Signed-off-by: Laszlo Kiraly <[email protected]>
ljkiraly
added a commit
to Nordix/nsm-sdk-kernel
that referenced
this issue
Oct 28, 2024
Issue: networkservicemesh#685 Try to delete the rule even if the route deletion fails. For example when the belonging interface is deleted in parallel. Signed-off-by: Laszlo Kiraly <[email protected]>
ljkiraly
added a commit
to Nordix/nsm-sdk-kernel
that referenced
this issue
Oct 28, 2024
Issue: networkservicemesh#685 Try to delete the rule even if the route deletion fails. For example when the belonging interface is deleted in parallel. Signed-off-by: Laszlo Kiraly <[email protected]>
Verification in progress. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some of the routes are missing from NSC. After deployment the routes were set but after a while they disappeared. The trigger is unknown.
The problem was seen on NSMv1.13.2.
In this topology 4 NS (one NSE provides one NS) and 4 NSC was deployed and each NSC connects to each NS. For one connection the routes are missing from NSC.
The relevant log printouts are already rotated out when the issue was detected.
The reproduction is in progress, but since we don't really know what caused this behavior it is difficult to provoke the issue.
The text was updated successfully, but these errors were encountered: