If a target application is discovered but is not initially connectable due to missing JMX credentials, then the target definition is retained but with a null/empty JVM ID. This appears in the Topology view as a target with the yellow warning exclamation mark. Adding a new Stored Credential that matches this target enables the Recording and Events views to work, but the Topology view continues to show the warning state.
Expected Behavior
After a matching Stored Credential is added, the Target should have its JVM ID set and the warning should disappear from the Topology view.
Steps To Reproduce
./smoktest.bash -t
go to Topology and see that two of the es.andrewazor.demo targets are in a warning state
add a stored credential: target.alias.contains('andrew'), admin:adminpass123
check Events view and ensure templates and types can be listed
Current Behavior
If a target application is discovered but is not initially connectable due to missing JMX credentials, then the target definition is retained but with a null/empty JVM ID. This appears in the Topology view as a target with the yellow warning exclamation mark. Adding a new Stored Credential that matches this target enables the Recording and Events views to work, but the Topology view continues to show the warning state.
Expected Behavior
After a matching Stored Credential is added, the Target should have its JVM ID set and the warning should disappear from the Topology view.
Steps To Reproduce
./smoktest.bash -tes.andrewazor.demotargets are in a warning statetarget.alias.contains('andrew'),admin:adminpass123Environment
No response
Anything else?