-
Notifications
You must be signed in to change notification settings - Fork 10
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
[Bug] Discovery Plugin registrations and deregistrations behave badly #406
Labels
bug
Something isn't working
Comments
|
This was referenced Apr 24, 2024
Done in #415 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current Behavior
When discovery plugins deregister an exception is thrown and the transaction is not committed. The discovery tree still contains the plugin's realm subtree.
Also, after a discovery plugin registers, it is visible in
GET /api/v3/discovery_plugins
and its subtree leaves inGET /api/v3/targets
, but it does not appear inGET /api/v3/discovery
(which also has the effect of making it not visible in the Topology view anymore).Expected Behavior
When discovery plugins deregister, they should be removed from the discovery tree along with all their targets. Each lost target should generate a WebSocket notification.
Steps To Reproduce
./smoketest.bash -t
podman stop compose_quarkus-test-agent_1
Environment
No response
Anything else?
No response
Probably related to #325 due to the new node
parent
field as well.The text was updated successfully, but these errors were encountered: