incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sumit Mohanty (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-2073) After Ambari upgrade to 1.2.3, MapReduce service check fails because uid of ambari_qa changed
Date Fri, 03 May 2013 21:04:15 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648802#comment-13648802
] 

Sumit Mohanty commented on AMBARI-2073:
---------------------------------------

Script itself looks good.

Few minor comments:
* Modify the comment - "Changing directory permisions" --> "Recursively changing directory
ownership"
* is "/tmp/changeUid.sh" the correct path for the script - how does it get copied to /tmp
* the name of the default qa user is changed from ambari_qa to ambari-qa (hyphen instead of
under_score)
** This should not be an issue as upgrade does not change the username. Just bringing it up
in case it has an effect.
                
> After Ambari upgrade to 1.2.3, MapReduce service check fails because uid of ambari_qa
changed
> ---------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-2073
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2073
>             Project: Ambari
>          Issue Type: Bug
>          Components: agent
>    Affects Versions: 1.3.0
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>             Fix For: 1.3.0
>
>         Attachments: AMBARI-2073.patch
>
>
> Directory details after upgrade when service check failed _not sure which user had the
uid 501_
> {noformat}
> drwxr-xr-x.  2    501 root   4096 Apr 30 19:25 hadoop-ambari_qa
> {noformat}
> After deleting the directory, MapRed service check passed.
> Details after successful run
> {noformat}
> drwxr-xr-x.  2 ambari_qa root   4096 Apr 30 22:39 hadoop-ambari_qa
> {noformat}

--
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

Mime
View raw message