[
https://issues.apache.org/jira/browse/SDAP-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503736#comment-16503736
]
ASF GitHub Bot commented on SDAP-107:
-------------------------------------
fgreg opened a new pull request #9: SDAP-107 Ningester container does not
report exit code correctly
URL: https://github.com/apache/incubator-sdap-ningester/pull/9
Because I was using a pipe to prepend text to every log line, when the java
command failed the exit status was being overwritten by the exit status of the
sed command effectively making it 0. This caused the container to exit with
code 0 and would show up as a successful job completion in kubernetes.
Fix was to use `set -o pipefail` in entrypoint script.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Ningester container does not report exit code correctly
> -------------------------------------------------------
>
> Key: SDAP-107
> URL: https://issues.apache.org/jira/browse/SDAP-107
> Project: Apache Science Data Analytics Platform
> Issue Type: Bug
> Components: nexus
> Reporter: Frank Greguska
> Assignee: Frank Greguska
> Priority: Major
>
> When the Spring batch job fails the exit code is being reported as 0 instead
> of non-zero to indicate failure. This is making debugging many jobs very
> difficult because it is impossible to determine which jobs failed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
