This issue is fixed in deployment manager 4.7, which will force kill any running test coverage sessions and starts a new one. As a work around skip the failing task and let the validate test coverage task run which will stop the test coverage session and the subsequent deployments will work fine.
Thanks Sahag. Is there any way to cancel any tracer sessions that are running? And is this application specific i.e, if the enable test coverage is used for application A in DM and being run, and if Tracer is running for Application B, will this still fail or this is independent?
Also is there any fix provided by pega to use it in same DM version instead of upgrading it to Ver 4.7?
Each test coverage session (For different applications) runs independently. For versions prior to 4.7, if you get this error saying a session is already in progress, you may need to login to the candidate system and go to the test coverage landing page to stop the ongoing session manually (You need the required privilege to do so). If not from pipeline, users can trigger a test coverage session manually from the application directly, which can cause this conflict sometimes.