Setting this to ON-DEV so that engineering can verify that this works in JON3.0.1 (i.e. branch release/jon3.0.x). As soon as its confirmed to work by engineering, it can go to ON-QA
This issue is confirmed to work in JON2.4.2 without any specific fixes. We're just testing this in JON3.0.1 to be thorough since its related to the agent registration fixes which need to go into the JON3.0.1 branch. Setting to ON-QA
(In reply to comment #2) > This issue is confirmed to work in JON2.4.2 without any specific fixes. We're > just testing this in JON3.0.1 to be thorough since its related to the agent > registration fixes which need to go into the JON3.0.1 branch. Setting to ON-QA fyi: nothing has been committed to the release/jon3.0.x branch yet.
Bulk closing of old issues in VERIFIED state.