hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8109) Using the default rpms of hadoop, /usr/etc/hadoop symlink gets removed on upgrade
Date Fri, 02 Mar 2012 18:09:59 GMT

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

Hadoop QA commented on HADOOP-8109:

-1 overall.  Here are the results of testing the latest attachment 
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/661//console

This message is automatically generated.
> Using the default rpms of hadoop,  /usr/etc/hadoop symlink gets removed on upgrade
> ----------------------------------------------------------------------------------
>                 Key: HADOOP-8109
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8109
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.23.0, 1.0.0
>            Reporter: Hitesh Shah
>            Assignee: Hitesh Shah
>            Priority: Minor
>         Attachments: HADOOP-8109.branch-1.patch, HADOOP-8109.trunk.patch
> Given that for rpms, the pre-uninstall scripts for the older version run after the post-install
scripts of the package being installed, the symlink created from /usr/etc/hadoop to /etc/hadoop
gets deleted. This breaks running /usr/bin/hadoop without providing --config. 

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


View raw message