After the recent update to the deployment chain I see that
ServerDeploymentStartStopHandler.activate(...)
is called before the ServerDeploymentRepository service comes up.
This results in a ServiceNotFoundException in ServerDeploymentStartStopHandler.getDeploymentRepository(...) which is then swallowed and does not show up on the console and neither in the logs.
As a result, deployements do silently not activate.