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

Posted to dev@bigtop.apache.org by "Peter Linnell (Updated) (JIRA)" <ji...@apache.org> on 2012/04/13 03:55:17 UTC

[jira] [Updated] (BIGTOP-528) A small patch to give better return codes which can be understood by chef and pupper among others.

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

Peter Linnell updated BIGTOP-528:
---------------------------------

    Attachment: BIGTOP-528.patch
    
> A small patch to give better return codes which can be understood by chef and pupper among others.
> --------------------------------------------------------------------------------------------------
>
>                 Key: BIGTOP-528
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-528
>             Project: Bigtop
>          Issue Type: Bug
>    Affects Versions: 0.3.0
>            Reporter: Peter Linnell
>            Priority: Minor
>             Fix For: 0.4.0
>
>         Attachments: BIGTOP-528.patch
>
>
> Configuration management tools like Puppet and Chef depend on exit codes. In case of the hadoop-hive-server package, the /etc/init.d/hadoop-hive-server status call provides zero exit code independent of the service running or not. This makes Chef believe that the service is running and there is no need to start it. The fix should be very easy, only changing the three occurances of the $status variable in the service's hive_status() function to $RETVAL.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira