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
Still the service is running as slave on node1 so it shouldn't be advertised as down
Restarting contrail-peering-monitor doesn't help
The text was updated successfully, but these errors were encountered:
I think this is because the Discovery continues to announce it. Otherwise it is a bug inexpected 😄 I will check that.
Sorry, something went wrong.
No branches or pull requests
Still the service is running as slave on node1 so it shouldn't be advertised as down
Restarting contrail-peering-monitor doesn't help
The text was updated successfully, but these errors were encountered: