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

Posted to issues@flink.apache.org by "Gabor Somogyi (Jira)" <ji...@apache.org> on 2022/12/05 09:06:00 UTC

[jira] [Resolved] (FLINK-30281) Parsing for log4j error entry instead of plain error string in e2e tests

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

Gabor Somogyi resolved FLINK-30281.
-----------------------------------
    Resolution: Fixed

[{{31e2e10}}|https://github.com/apache/flink-kubernetes-operator/commit/31e2e10f112385120ac44378eaaa2e39b338ea61] on main

> Parsing for log4j error entry instead of plain error string in e2e tests
> ------------------------------------------------------------------------
>
>                 Key: FLINK-30281
>                 URL: https://issues.apache.org/jira/browse/FLINK-30281
>             Project: Flink
>          Issue Type: Bug
>          Components: Kubernetes Operator
>            Reporter: Gabor Somogyi
>            Assignee: Gabor Somogyi
>            Priority: Major
>              Labels: pull-request-available
>
> Error which came up:
> [https://github.com/gaborgsomogyi/flink-kubernetes-operator/actions/runs/3601102650/jobs/6066522997#step:9:121]
> {code:java}
> Found error in log files.
> flink-kubernetes-operator-7456697448-mgw42.k8soperator.flink.flink-kubernetes-operator.namespace.default.FlinkDeployment.JmDeploymentStatus.ERROR.Count: 0
> 121 {code}



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