I started the task with the forceRemoval option, but it appears to have shutdown the controller VM only and is stuck on REMOVING.

An extract from https://msx-mgr-ip/api/2.0/vdn/controller:

<status>REMOVING</status>
<upgradeStatus>UPGRADED</upgradeStatus>
<version>6.3.7073587</version>
<upgradeAvailable>false</upgradeAvailable>

I think the corresponding log entry is this:

"ERROR TaskFrameworkExecutor-3 ControllerRemovalTask:324 - cannot get controller node uuid / remove node from cluster"

any idea how I can bypass this and delete the controller? this is an old test environment where all controllers were showing disconnected and I need to redeploy...