You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Nicholas Jiang (Jira)" <ji...@apache.org> on 2022/03/17 08:06:00 UTC

[jira] (FLINK-26695) Fabric8FlinkKubeClient.deleteConfigMap and deleteConfigMapsByLabels don't necessarily fail if the deletion didn't succeed

    [ https://issues.apache.org/jira/browse/FLINK-26695 ]


    Nicholas Jiang deleted comment on FLINK-26695:
    ----------------------------------------

was (Author: nicholasjiang):
[~wangyang0918], as you said, this should add the check whether the  deleted ConfigMaps are existed and retry the deletion when delete the ConfigMaps exception, right?

> Fabric8FlinkKubeClient.deleteConfigMap and deleteConfigMapsByLabels don't necessarily fail if the deletion didn't succeed
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-26695
>                 URL: https://issues.apache.org/jira/browse/FLINK-26695
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / Kubernetes, Runtime / Coordination
>    Affects Versions: 1.15.0, 1.16.0
>            Reporter: Matthias Pohl
>            Priority: Major
>
> {{Fabric8FlinkKubeClient.deleteConfigMap}} and {{deleteConfigMapsByLabels}} do not evaluate the return value and, therefore, might miss an error during deletion.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)