The GitHub Actions job "Flink Kubernetes Operator CI" on flink-kubernetes-operator.git/FLINK-40470-savepoint-redeploy-status-before-deploy has succeeded. Run started by GitHub user hyeonkimmm (triggered by rmetzger).
Head commit for run: de65baef7acca4dd6ed1f08e5a542b7281bf3e36 / hyeonkimmm <[email protected]> [FLINK-40470] Record spec before deployment attempt in savepoint redeploy When job.savepointRedeployNonce changes, redeployWithSavepoint cancels the running job and redeploys it from initialSavepointPath. Unlike every other deployment path it only recorded the target spec in the status after the deploy call succeeded. If deploy threw (transient API server error, or an error raised after the cluster resources were already created), the new nonce never reached lastReconciledSpec, every subsequent reconciliation classified the diff as SAVEPOINT_REDEPLOY again and the operator repeated the cancel + redeploy cycle indefinitely. Record the target spec with updateStatusBeforeDeploymentAttempt before the deploy call, mirroring the suspend/resume path, so that a failed attempt is retried through the regular restore path from the recorded upgradeSavepointPath. The suspended -> running path used to fall back to an empty state restore whenever the spec declared upgradeMode: stateless. This discarded the initialSavepointPath of a savepoint redeploy requested while suspended, and would have turned the retry above into an empty state restore for stateless jobs. A savepoint the user explicitly requested through initialSavepointPath, recorded as the upgrade savepoint by the redeploy, is now restored regardless of the upgrade mode. Resuming a job suspended in savepoint or last-state mode with a stateless spec still starts from empty state, as before. Generated-by: Claude Code (Claude Fable 5.1) Report URL: https://github.com/apache/flink-kubernetes-operator/actions/runs/36571208735 With regards, GitHub Actions via GitBox
