Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
None
Description
Currently we don't have a good way of asserting that the job never started after savepoint upgrade when the JM deployment fails (such as on an incorrect image).
This easily leads to scenarios which require manual recovery from the user.
We should try to avoid this with some mechanism to greately improve the robustness of savepoint ugrades.