We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The following issue has been noticed while running multi-stream test:
Periodically, nsm- interfaces are not wiped out from the list of interfaces after the target pod is disconnected from the stream-n.
The multi-stream test goes as follows:
During some test runs, it was noticed that after even the last step (6th), the nsm- interfaces were still present in some target pods.
An example of the system during the test run is provided: the nsm-1 interface is stuck in the target pod -ctj6w
The text was updated successfully, but these errors were encountered:
It might be the same problem as I have when I try to run the new-attractor-nsm-vlan e2e test: #343
new-attractor-nsm-vlan
Sorry, something went wrong.
Related to: networkservicemesh/sdk#1434
networkservicemesh/deployments-k8s#8882
No branches or pull requests
The following issue has been noticed while running multi-stream test:
Periodically, nsm- interfaces are not wiped out from the list of interfaces after the target pod is disconnected from the stream-n.
The multi-stream test goes as follows:
During some test runs, it was noticed that after even the last step (6th), the nsm- interfaces were still present in some target pods.
An example of the system during the test run is provided: the nsm-1 interface is stuck in the target pod -ctj6w
The text was updated successfully, but these errors were encountered: