[ https://issues.apache.org/jira/browse/HADOOP-12468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14949725#comment-14949725 ]
Hadoop QA commented on HADOOP-12468: ------------------------------------ \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | pre-patch | 17m 33s | Pre-patch trunk compilation is healthy. | | {color:green}+1{color} | @author | 0m 0s | The patch does not contain any @author tags. | | {color:green}+1{color} | tests included | 0m 0s | The patch appears to include 1 new or modified test files. | | {color:green}+1{color} | javac | 8m 3s | There were no new javac warning messages. | | {color:green}+1{color} | javadoc | 10m 24s | There were no new javadoc warning messages. | | {color:red}-1{color} | release audit | 0m 19s | The applied patch generated 1 release audit warnings. | | {color:green}+1{color} | checkstyle | 1m 9s | There were no new checkstyle issues. | | {color:green}+1{color} | whitespace | 0m 0s | The patch has no lines that end in whitespace. | | {color:green}+1{color} | install | 1m 30s | mvn install still works. | | {color:green}+1{color} | eclipse:eclipse | 0m 33s | The patch built with eclipse:eclipse. | | {color:green}+1{color} | findbugs | 1m 52s | The patch does not introduce any new Findbugs (version 3.0.0) warnings. | | {color:red}-1{color} | common tests | 7m 37s | Tests failed in hadoop-common. | | | | 49m 4s | | \\ \\ || Reason || Tests || | Failed unit tests | hadoop.metrics2.impl.TestGangliaMetrics | \\ \\ || Subsystem || Report/Notes || | Patch URL | http://issues.apache.org/jira/secure/attachment/12765706/HADOOP-12468.001.patch | | Optional Tests | javadoc javac unit findbugs checkstyle | | git revision | trunk / 8d22622 | | Release Audit | https://builds.apache.org/job/PreCommit-HADOOP-Build/7785/artifact/patchprocess/patchReleaseAuditProblems.txt | | hadoop-common test log | https://builds.apache.org/job/PreCommit-HADOOP-Build/7785/artifact/patchprocess/testrun_hadoop-common.txt | | Test Results | https://builds.apache.org/job/PreCommit-HADOOP-Build/7785/testReport/ | | Java | 1.7.0_55 | | uname | Linux asf903.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux | | Console output | https://builds.apache.org/job/PreCommit-HADOOP-Build/7785/console | This message was automatically generated. > Partial group resolution failure should not result in user lockout > ------------------------------------------------------------------ > > Key: HADOOP-12468 > URL: https://issues.apache.org/jira/browse/HADOOP-12468 > Project: Hadoop Common > Issue Type: Bug > Components: security > Affects Versions: 2.6.1 > Environment: Linux > Reporter: Wei-Chiu Chuang > Assignee: Wei-Chiu Chuang > Priority: Minor > Attachments: HADOOP-12468.001.patch > > > If a Hadoop cluster is configured to use ShellBasedUnixGroupsMapping for > user/group name mapping, occasionally some group names may become > unresolvable (for example, using SSSD). > ShellBasedUnixGroupsMapping uses shell command "id -Gn" to retrieve the group > name of a user; however, the existing logic assumes that if the exit code of > the command is non-zero, the user has no group name at all. The shell command > in Linux returns non-zero exit code if a group name is not resolvable. > Unfortunately, it is possible that a user belongs to multiple groups, and any > partial failure in group name resolution would denied the user's access. > On the other hand, the JNI implementation (JniBasedUnixGroupsMapping) is more > resilient. If any group name is unresolvable, it is simply ignored, and > whatever are resolvable are returned. > It is arguable that if the group name is not resolvable, the administrator > should configure their directory/authentication service correctly, and Hadoop > is in no position to handle it, but since the existing unit tests assume the > output of JNI-based and shell-based implementation are the same, we should > improve the shell-based group name resolution, and make it as resilient as > the JNI-based one. -- This message was sent by Atlassian JIRA (v6.3.4#6332)