whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Bayer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (WHIRR-653) Script exit codes aren't being checked
Date Mon, 25 Mar 2013 22:59:15 GMT

    [ https://issues.apache.org/jira/browse/WHIRR-653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613271#comment-13613271

Andrew Bayer commented on WHIRR-653:

This would be valuable, but will necessitate making sure we actually have meaningful exit
codes in all the existing scripts, and may also mean changing the aggregate bootstrap and
configure scripts to exit on error, rather than just passing the last exit code it hits to
the caller. Will look at soon.
> Script exit codes aren't being checked
> --------------------------------------
>                 Key: WHIRR-653
>                 URL: https://issues.apache.org/jira/browse/WHIRR-653
>             Project: Whirr
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.9.0
>         Environment: local: OSX, remote RHEL6.3
>            Reporter: Steve Loughran
>            Assignee: Andrew Bayer
>            Priority: Critical
>             Fix For: 0.9.0
>         Attachments: whirr-653.patch
> My installer script bails out with an {{exit 1}} on many operations, such as
> {{chown -R hadoop:hadoop $HADOOP_PID_DIR  || exit 1;}}
> This is to find problems early and so aid debugging of the installation.
> Even when a script fails this way, Whirr declares that the installation was successful.

> It must check the return codes to be confident that the operation succeeded.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message