Hi guys,

We developed some scripts to improve the rolling updates in our pipelines,
and one of the tasks done is to trigger a savepoint and waits for the
response until the status is Completed or until it achieves the limit of
retries.

It was noticed that sometimes the response has the status Completed but the
request failed:

{
    "status": {
        "id": "COMPLETED"
    },
    "operation": {
        "failure-cause": {
            "class": "java.util.concurrent.CompletionException",
            "stack-trace": "java.util.concurrent.CompletionException: ....
)\n\t... 47 more\n",
            "serialized-throwable": "..."
        }
    }
}

An easy way to reproduce the issue is to put the job in a restart loop and
trigger a savepoint.

Should the status be in-progress, right?

Reply via email to