[ 
https://issues.apache.org/jira/browse/FLINK-38033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Salva updated FLINK-38033:
--------------------------
    Description: 
I was running Flink Kubernetes Operator 1.11 and everything was fine. However, 
after upgrading to 1.12, the operator is misbehaving like this during job 
upgrades:
 * First, it takes a savepoint as usual
 * Then it uploads it to S3 as usual too
 * ...but after that, for some reason, it disposes/deletes it! 
 * This makes the job upgrade fail

I downgraded the operator to 1.11 and job upgrades started to work again.

  was:
I was running Flink Kubernetes Operator v1.11 with a minor tweak that I 
introduced in v1.10, see more here:
 * [https://lists.apache.org/thread/b9gkso9wvwp2s19dn7s1ol5b9okbbtwq]

and everything was fine. However, after upgrading to v1.12, the operator is 
misbehaving like this during job upgrades:
 * First, it takes a savepoint as usual
 * Then it uploads it to S3 as usual too
 * ...but after that, for some reason, it disposes/deletes it! 
 * This makes the job upgrade fail

I downgraded the operator to v1.11 and job upgrades started to work again.


> Job upgrades fail for operator v1.12
> ------------------------------------
>
>                 Key: FLINK-38033
>                 URL: https://issues.apache.org/jira/browse/FLINK-38033
>             Project: Flink
>          Issue Type: Bug
>          Components: Autoscaler, Kubernetes Operator
>    Affects Versions: kubernetes-operator-1.12.0
>         Environment: * Flink 1.18.1
>  * Flink Kubernetes Operator 1.12 
>            Reporter: Salva
>            Priority: Major
>
> I was running Flink Kubernetes Operator 1.11 and everything was fine. 
> However, after upgrading to 1.12, the operator is misbehaving like this 
> during job upgrades:
>  * First, it takes a savepoint as usual
>  * Then it uploads it to S3 as usual too
>  * ...but after that, for some reason, it disposes/deletes it! 
>  * This makes the job upgrade fail
> I downgraded the operator to 1.11 and job upgrades started to work again.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to