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

[Bug] Cannot delete custom targets that no longer point to a JVM #1866

Open
andrewazores opened this issue Jan 25, 2024 · 0 comments
Open

[Bug] Cannot delete custom targets that no longer point to a JVM #1866

andrewazores opened this issue Jan 25, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@andrewazores
Copy link
Member

Current Behavior

To replicate it create a custom target and use the service in the connection URL, the remove the port 9091 from the service
the pod restart when I try to open the recordings for the custom target
cannot delete custom target from topology view

I think this can be tested in the smoketest by running a target application with JDP turned off and without Podman discovery annotations, so that it is present but not discoverable by default. Then define a custom target pointing to it. Then podman stop the target application, and podman run to restart it but this time with a different JMX port (or none).

The first "pod restart" issue is probably #1778 .

The "cannot delete custom target" seems related but may be a different bug.

Expected Behavior

No response

Steps To Reproduce

No response

Environment

No response

Anything else?

No response

@andrewazores andrewazores added the bug Something isn't working label Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
No open projects
Status: No status
Development

No branches or pull requests

1 participant