Details
-
Improvement
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
kubernetes-operator-1.0.0
Description
Seems like in some weird cornercases when we observe the FINISHED job (stopped with savepoint) during an upgrade the recorded last snapshot is incorrect (still need to investigate if this is due to a Flink problem or what) This can lead to upgrade errors.
This can be avoided by simply skipping the observe step when the reconciliation status is UPGRADING because at that point we actually know that the job was already shut down and state recorded correctly in the savepoint info.
Attachments
Issue Links
- links to