Currently the cluster tests don't include having a worker terminate during the launch procedure. I expect the current behaviour would cause the launch to be terminated due to an uncaught exception being raised (either while waiting for the pod to be running or while the manager attempts to connect).
Currently the cluster tests don't include having a worker terminate during the launch procedure. I expect the current behaviour would cause the launch to be terminated due to an uncaught exception being raised (either while waiting for the pod to be running or while the manager attempts to connect).