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

Hudson commented on HADOOP-7811:
--------------------------------

Integrated in Hadoop-Common-trunk-Commit #1275 (See 
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/1275/])
    HADOOP-7811. TestUserGroupInformation#testGetServerSideGroups test fails in 
chroot. (Jonathan Eagles via mahadev)

mahadev : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1202540
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/security/TestUserGroupInformation.java

                
> TestUserGroupInformation#testGetServerSideGroups test fails in chroot
> ---------------------------------------------------------------------
>
>                 Key: HADOOP-7811
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7811
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security, test
>    Affects Versions: 0.23.1
>            Reporter: Jonathan Eagles
>            Assignee: Jonathan Eagles
>             Fix For: 0.23.1
>
>         Attachments: HADOOP-7811.patch
>
>
> It is common when running in chroot to have root's group vector preserved 
> when running as your self.
> For example
> # Enter chroot
> $ sudo chroot /myroot
> # still root
> $ whoami
> root
> # switch to user preserving root's group vector
> $ sudo -u user -P -s
> # root's groups
> $ groups root
> a b c
> # user's real groups
> $ groups user
> d e f
> # user's effective groups
> $ groups
> a b c d e f
> -------------------------------

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

        

Reply via email to