Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-12296

when setnetgrent returns 0 in linux, exception should be thrown

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.8.0, 2.7.3, 3.0.0-alpha1
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      In linux, setnetgrent returns 0 in linux when something wrong is happen, such as out of memory, unknown group, unavailable service, etc. So errorMessage should be set and exception should be thrown

      1. HADOOP-12296.patch
        1.0 kB
        Chang Li
      2. HADOOP-12296.2.patch
        0.9 kB
        Chang Li
      3. HADOOP-12296.3.patch
        2 kB
        Chang Li
      4. HADOOP-12296.3.patch
        2 kB
        Chang Li

        Activity

        Hide
        lichangleo Chang Li added a comment -

        Jason Lowe please help review, thanks!

        Show
        lichangleo Chang Li added a comment - Jason Lowe please help review, thanks!
        Hide
        aw Allen Wittenauer added a comment -

        This code change covers more than Linux. We need to verify it on Solaris/Illumos at a minimum.

        Show
        aw Allen Wittenauer added a comment - This code change covers more than Linux. We need to verify it on Solaris/Illumos at a minimum.
        Hide
        lichangleo Chang Li added a comment -

        Allen Wittenauer thanks for review. Uploaded .2 patch which will only cover Linux.

        Show
        lichangleo Chang Li added a comment - Allen Wittenauer thanks for review. Uploaded .2 patch which will only cover Linux.
        Hide
        aw Allen Wittenauer added a comment -

        Is throwing an exception really the correct thing to do when a netgroup doesn't exist? That seems particularly drastic.

        Show
        aw Allen Wittenauer added a comment - Is throwing an exception really the correct thing to do when a netgroup doesn't exist? That seems particularly drastic.
        Hide
        hadoopqa Hadoop QA added a comment -



        -1 overall



        Vote Subsystem Runtime Comment
        0 pre-patch 5m 22s Pre-patch trunk compilation is healthy.
        +1 @author 0m 0s The patch does not contain any @author tags.
        -1 tests included 0m 0s 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 javac 7m 39s There were no new javac warning messages.
        +1 release audit 0m 18s The applied patch does not increase the total number of release audit warnings.
        +1 whitespace 0m 0s The patch has no lines that end in whitespace.
        +1 install 1m 21s mvn install still works.
        +1 eclipse:eclipse 0m 30s The patch built with eclipse:eclipse.
        +1 common tests 22m 12s Tests passed in hadoop-common.
            37m 25s  



        Subsystem Report/Notes
        Patch URL http://issues.apache.org/jira/secure/attachment/12748541/HADOOP-12296.2.patch
        Optional Tests javac unit
        git revision trunk / 469cfcd
        hadoop-common test log https://builds.apache.org/job/PreCommit-HADOOP-Build/7405/artifact/patchprocess/testrun_hadoop-common.txt
        Test Results https://builds.apache.org/job/PreCommit-HADOOP-Build/7405/testReport/
        Java 1.7.0_55
        uname Linux asf907.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/7405/console

        This message was automatically generated.

        Show
        hadoopqa Hadoop QA added a comment - -1 overall Vote Subsystem Runtime Comment 0 pre-patch 5m 22s Pre-patch trunk compilation is healthy. +1 @author 0m 0s The patch does not contain any @author tags. -1 tests included 0m 0s 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 javac 7m 39s There were no new javac warning messages. +1 release audit 0m 18s The applied patch does not increase the total number of release audit warnings. +1 whitespace 0m 0s The patch has no lines that end in whitespace. +1 install 1m 21s mvn install still works. +1 eclipse:eclipse 0m 30s The patch built with eclipse:eclipse. +1 common tests 22m 12s Tests passed in hadoop-common.     37m 25s   Subsystem Report/Notes Patch URL http://issues.apache.org/jira/secure/attachment/12748541/HADOOP-12296.2.patch Optional Tests javac unit git revision trunk / 469cfcd hadoop-common test log https://builds.apache.org/job/PreCommit-HADOOP-Build/7405/artifact/patchprocess/testrun_hadoop-common.txt Test Results https://builds.apache.org/job/PreCommit-HADOOP-Build/7405/testReport/ Java 1.7.0_55 uname Linux asf907.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/7405/console This message was automatically generated.
        Hide
        lichangleo Chang Li added a comment -

        Allen Wittenauer thanks for providing opinion. But I still think it's reasonable to thrown an exception because when setnetgrent returns 0 in linux it's not saying the netgroup is empty, but it's actually saying the passed netgroup name is invalid (misconfigured) or if any error occurred.

        Show
        lichangleo Chang Li added a comment - Allen Wittenauer thanks for providing opinion. But I still think it's reasonable to thrown an exception because when setnetgrent returns 0 in linux it's not saying the netgroup is empty, but it's actually saying the passed netgroup name is invalid (misconfigured) or if any error occurred.
        Hide
        jlowe Jason Lowe added a comment -

        Is throwing an exception really the correct thing to do when a netgroup doesn't exist? That seems particularly drastic.

        Throwing an exception makes sense to me given the context in which this is used. This code is only called in one place, and here's what it does:

        JniBasedUnixGroupsNetgroupMapping.java
          protected synchronized List<String> getUsersForNetgroup(String netgroup) {
            String[] users = null;
            try {
              // JNI code does not expect '@' at the begining of the group name
              users = getUsersForNetgroupJNI(netgroup.substring(1));
            } catch (Exception e) {
              if (LOG.isDebugEnabled()) {
                LOG.debug("Error getting users for netgroup " + netgroup, e);
              } else {
                LOG.info("Error getting users for netgroup " + netgroup + 
                    ": " + e.getMessage());
              }
            }
            if (users != null && users.length != 0) {
              return Arrays.asList(users);
            }
            return new LinkedList<String>();
          }
        

        As it is today, setnetgrent errors are silently ignored. The C code behaves as if the netgroup exists but is empty. No error or warning is logged, so if someone accidentally specifies a bogus netgroup in some ACL conf property (e.g.: who has access to this scheduler queue) or if there's a problem performing the lookup on a particular netgroup then there will be no diagnostic whatsoever. That's not very helpful when someone is trying to figure out why permissions aren't working properly. If we start throwing an exception when setnetgrent fails then we will still act as if the netgroup exists and is empty, but at least we'll log a message indicating something went wrong with that netgroup lookup.

        Chang Li have you tested this change?

        Show
        jlowe Jason Lowe added a comment - Is throwing an exception really the correct thing to do when a netgroup doesn't exist? That seems particularly drastic. Throwing an exception makes sense to me given the context in which this is used. This code is only called in one place, and here's what it does: JniBasedUnixGroupsNetgroupMapping.java protected synchronized List< String > getUsersForNetgroup( String netgroup) { String [] users = null ; try { // JNI code does not expect '@' at the begining of the group name users = getUsersForNetgroupJNI(netgroup.substring(1)); } catch (Exception e) { if (LOG.isDebugEnabled()) { LOG.debug( "Error getting users for netgroup " + netgroup, e); } else { LOG.info( "Error getting users for netgroup " + netgroup + ": " + e.getMessage()); } } if (users != null && users.length != 0) { return Arrays.asList(users); } return new LinkedList< String >(); } As it is today, setnetgrent errors are silently ignored. The C code behaves as if the netgroup exists but is empty. No error or warning is logged, so if someone accidentally specifies a bogus netgroup in some ACL conf property (e.g.: who has access to this scheduler queue) or if there's a problem performing the lookup on a particular netgroup then there will be no diagnostic whatsoever. That's not very helpful when someone is trying to figure out why permissions aren't working properly. If we start throwing an exception when setnetgrent fails then we will still act as if the netgroup exists and is empty, but at least we'll log a message indicating something went wrong with that netgroup lookup. Chang Li have you tested this change?
        Hide
        lichangleo Chang Li added a comment -

        Jason Lowe thanks for review! Actually after test .2 I found out that it didn't use the THROW macro right. Uploaded .3 patch with right usage of THROW and also change some misleading naming in the c file. I test that the .3 patch throw the right exception and also get logged correctly. Below is log I get for the test.

          Error getting users for netgroup @lasVegas: no netgroup of this name is known or some other error occurred
        Show
        lichangleo Chang Li added a comment - Jason Lowe thanks for review! Actually after test .2 I found out that it didn't use the THROW macro right. Uploaded .3 patch with right usage of THROW and also change some misleading naming in the c file. I test that the .3 patch throw the right exception and also get logged correctly. Below is log I get for the test. Error getting users for netgroup @lasVegas: no netgroup of this name is known or some other error occurred
        Hide
        hadoopqa Hadoop QA added a comment -



        -1 overall



        Vote Subsystem Runtime Comment
        0 pre-patch 5m 41s Pre-patch trunk compilation is healthy.
        +1 @author 0m 0s The patch does not contain any @author tags.
        -1 tests included 0m 0s 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 javac 8m 10s There were no new javac warning messages.
        +1 release audit 0m 20s The applied patch does not increase the total number of release audit warnings.
        +1 whitespace 0m 0s The patch has no lines that end in whitespace.
        +1 install 1m 25s mvn install still works.
        +1 eclipse:eclipse 0m 33s The patch built with eclipse:eclipse.
        -1 common tests 22m 27s Tests failed in hadoop-common.
            38m 39s  



        Reason Tests
        Failed unit tests hadoop.ipc.TestCallQueueManager



        Subsystem Report/Notes
        Patch URL http://issues.apache.org/jira/secure/attachment/12748901/HADOOP-12296.3.patch
        Optional Tests javac unit
        git revision trunk / 4ab49a4
        hadoop-common test log https://builds.apache.org/job/PreCommit-HADOOP-Build/7415/artifact/patchprocess/testrun_hadoop-common.txt
        Test Results https://builds.apache.org/job/PreCommit-HADOOP-Build/7415/testReport/
        Java 1.7.0_55
        uname Linux asf905.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/7415/console

        This message was automatically generated.

        Show
        hadoopqa Hadoop QA added a comment - -1 overall Vote Subsystem Runtime Comment 0 pre-patch 5m 41s Pre-patch trunk compilation is healthy. +1 @author 0m 0s The patch does not contain any @author tags. -1 tests included 0m 0s 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 javac 8m 10s There were no new javac warning messages. +1 release audit 0m 20s The applied patch does not increase the total number of release audit warnings. +1 whitespace 0m 0s The patch has no lines that end in whitespace. +1 install 1m 25s mvn install still works. +1 eclipse:eclipse 0m 33s The patch built with eclipse:eclipse. -1 common tests 22m 27s Tests failed in hadoop-common.     38m 39s   Reason Tests Failed unit tests hadoop.ipc.TestCallQueueManager Subsystem Report/Notes Patch URL http://issues.apache.org/jira/secure/attachment/12748901/HADOOP-12296.3.patch Optional Tests javac unit git revision trunk / 4ab49a4 hadoop-common test log https://builds.apache.org/job/PreCommit-HADOOP-Build/7415/artifact/patchprocess/testrun_hadoop-common.txt Test Results https://builds.apache.org/job/PreCommit-HADOOP-Build/7415/testReport/ Java 1.7.0_55 uname Linux asf905.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/7415/console This message was automatically generated.
        Hide
        jlowe Jason Lowe added a comment -

        Latest patch looks good, at least from the Linux perspective. Can anyone comment on the other architectures that are returning a value from setnetgrent? Seems to me that we would want to report an error for the other architectures that are returning an error, otherwise we are silently not loading anything for the netgroup on those platforms. As I mentioned above, the only difference in practice is whether we log a message when this occurs or not, so I think we should remove the _linux_ check. Thoughts?

        Show
        jlowe Jason Lowe added a comment - Latest patch looks good, at least from the Linux perspective. Can anyone comment on the other architectures that are returning a value from setnetgrent? Seems to me that we would want to report an error for the other architectures that are returning an error, otherwise we are silently not loading anything for the netgroup on those platforms. As I mentioned above, the only difference in practice is whether we log a message when this occurs or not, so I think we should remove the _ linux _ check. Thoughts?
        Hide
        lichangleo Chang Li added a comment -

        Jason Lowe, thanks for review and valuable feedback! But for architecture of Solaris/Illumos, setnetgrent return 0 upon success. So should we limit the scope of fix of this patch only to linux?

        Show
        lichangleo Chang Li added a comment - Jason Lowe , thanks for review and valuable feedback! But for architecture of Solaris/Illumos, setnetgrent return 0 upon success. So should we limit the scope of fix of this patch only to linux?
        Hide
        jlowe Jason Lowe added a comment -

        But for architecture of Solaris/Illumos, setnetgrent return 0 upon success.

        Argh, looks like that is the case. So helpful that the two architectures decided to do the exact opposite on the return value.

        I'm +1 for the .3 patch then, since at least Linux will log something when an error occurs. Will commit this tomorrow if there are no objections.

        Show
        jlowe Jason Lowe added a comment - But for architecture of Solaris/Illumos, setnetgrent return 0 upon success. Argh, looks like that is the case. So helpful that the two architectures decided to do the exact opposite on the return value. I'm +1 for the .3 patch then, since at least Linux will log something when an error occurs. Will commit this tomorrow if there are no objections.
        Hide
        aw Allen Wittenauer added a comment -

        So helpful that the two architectures decided to do the exact opposite on the return value.

        Given netgroup was in Sun operating systems since before Linux even existed....

        Show
        aw Allen Wittenauer added a comment - So helpful that the two architectures decided to do the exact opposite on the return value. Given netgroup was in Sun operating systems since before Linux even existed....
        Hide
        hadoopqa Hadoop QA added a comment -
        -1 overall



        Vote Subsystem Runtime Comment
        0 reexec 0m 7s docker + precommit patch detected.
        +1 @author 0m 0s The patch does not contain any @author tags.
        -1 test4tests 0m 0s 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 mvninstall 3m 10s trunk passed
        +1 compile 4m 16s trunk passed with JDK v1.8.0_60
        +1 compile 4m 16s trunk passed with JDK v1.7.0_79
        +1 mvneclipse 0m 13s trunk passed
        +1 mvninstall 1m 27s the patch passed
        +1 compile 4m 25s the patch passed with JDK v1.8.0_60
        +1 cc 4m 25s the patch passed
        +1 javac 4m 25s the patch passed
        +1 compile 4m 5s the patch passed with JDK v1.7.0_79
        +1 cc 4m 5s the patch passed
        +1 javac 4m 5s the patch passed
        +1 mvneclipse 0m 14s the patch passed
        +1 whitespace 0m 0s Patch has no whitespace issues.
        -1 unit 6m 57s hadoop-common in the patch failed with JDK v1.8.0_60.
        +1 unit 7m 58s hadoop-common in the patch passed with JDK v1.7.0_79.
        +1 asflicense 0m 23s Patch does not generate ASF License warnings.
        37m 38s



        Reason Tests
        JDK v1.8.0_60 Failed junit tests hadoop.metrics2.impl.TestGangliaMetrics



        Subsystem Report/Notes
        Docker Client=1.7.1 Server=1.7.1 Image:test-patch-base-hadoop-date2015-11-02
        JIRA Patch URL https://issues.apache.org/jira/secure/attachment/12748901/HADOOP-12296.3.patch
        JIRA Issue HADOOP-12296
        Optional Tests asflicense cc unit javac compile
        uname Linux 9f64038b1c21 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
        Build tool maven
        Personality /home/jenkins/jenkins-slave/workspace/PreCommit-HADOOP-Build/patchprocess/apache-yetus-e77b1ce/precommit/personality/hadoop.sh
        git revision trunk / 9e7dcab
        Default Java 1.7.0_79
        Multi-JDK versions /usr/lib/jvm/java-8-oracle:1.8.0_60 /usr/lib/jvm/java-7-openjdk-amd64:1.7.0_79
        unit https://builds.apache.org/job/PreCommit-HADOOP-Build/7999/artifact/patchprocess/patch-unit-hadoop-common-project_hadoop-common-jdk1.8.0_60.txt
        unit test logs https://builds.apache.org/job/PreCommit-HADOOP-Build/7999/artifact/patchprocess/patch-unit-hadoop-common-project_hadoop-common-jdk1.8.0_60.txt
        JDK v1.7.0_79 Test Results https://builds.apache.org/job/PreCommit-HADOOP-Build/7999/testReport/
        modules C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common
        Max memory used 229MB
        Powered by Apache Yetus http://yetus.apache.org
        Console output https://builds.apache.org/job/PreCommit-HADOOP-Build/7999/console

        This message was automatically generated.

        Show
        hadoopqa Hadoop QA added a comment - -1 overall Vote Subsystem Runtime Comment 0 reexec 0m 7s docker + precommit patch detected. +1 @author 0m 0s The patch does not contain any @author tags. -1 test4tests 0m 0s 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 mvninstall 3m 10s trunk passed +1 compile 4m 16s trunk passed with JDK v1.8.0_60 +1 compile 4m 16s trunk passed with JDK v1.7.0_79 +1 mvneclipse 0m 13s trunk passed +1 mvninstall 1m 27s the patch passed +1 compile 4m 25s the patch passed with JDK v1.8.0_60 +1 cc 4m 25s the patch passed +1 javac 4m 25s the patch passed +1 compile 4m 5s the patch passed with JDK v1.7.0_79 +1 cc 4m 5s the patch passed +1 javac 4m 5s the patch passed +1 mvneclipse 0m 14s the patch passed +1 whitespace 0m 0s Patch has no whitespace issues. -1 unit 6m 57s hadoop-common in the patch failed with JDK v1.8.0_60. +1 unit 7m 58s hadoop-common in the patch passed with JDK v1.7.0_79. +1 asflicense 0m 23s Patch does not generate ASF License warnings. 37m 38s Reason Tests JDK v1.8.0_60 Failed junit tests hadoop.metrics2.impl.TestGangliaMetrics Subsystem Report/Notes Docker Client=1.7.1 Server=1.7.1 Image:test-patch-base-hadoop-date2015-11-02 JIRA Patch URL https://issues.apache.org/jira/secure/attachment/12748901/HADOOP-12296.3.patch JIRA Issue HADOOP-12296 Optional Tests asflicense cc unit javac compile uname Linux 9f64038b1c21 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 Build tool maven Personality /home/jenkins/jenkins-slave/workspace/PreCommit-HADOOP-Build/patchprocess/apache-yetus-e77b1ce/precommit/personality/hadoop.sh git revision trunk / 9e7dcab Default Java 1.7.0_79 Multi-JDK versions /usr/lib/jvm/java-8-oracle:1.8.0_60 /usr/lib/jvm/java-7-openjdk-amd64:1.7.0_79 unit https://builds.apache.org/job/PreCommit-HADOOP-Build/7999/artifact/patchprocess/patch-unit-hadoop-common-project_hadoop-common-jdk1.8.0_60.txt unit test logs https://builds.apache.org/job/PreCommit-HADOOP-Build/7999/artifact/patchprocess/patch-unit-hadoop-common-project_hadoop-common-jdk1.8.0_60.txt JDK v1.7.0_79 Test Results https://builds.apache.org/job/PreCommit-HADOOP-Build/7999/testReport/ modules C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common Max memory used 229MB Powered by Apache Yetus http://yetus.apache.org Console output https://builds.apache.org/job/PreCommit-HADOOP-Build/7999/console This message was automatically generated.
        Hide
        jlowe Jason Lowe added a comment -

        Test failure is unrelated, and it passes for me locally with JDK8. Commiting this.

        Show
        jlowe Jason Lowe added a comment - Test failure is unrelated, and it passes for me locally with JDK8. Commiting this.
        Hide
        jlowe Jason Lowe added a comment -

        Thanks to Chang for the contribution and to Allen for additional review! I committed this to trunk, branch-2, and branch-2.7.

        Show
        jlowe Jason Lowe added a comment - Thanks to Chang for the contribution and to Allen for additional review! I committed this to trunk, branch-2, and branch-2.7.
        Hide
        hudson Hudson added a comment -

        FAILURE: Integrated in Hadoop-trunk-Commit #8755 (See https://builds.apache.org/job/Hadoop-trunk-Commit/8755/)
        HADOOP-12296. when setnetgrent returns 0 in linux, exception should be (jlowe: rev b9d25c3ee2d20166d6a786c5a16cc001e249f61c)

        • hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/security/JniBasedUnixGroupsNetgroupMapping.c
        • hadoop-common-project/hadoop-common/CHANGES.txt
        Show
        hudson Hudson added a comment - FAILURE: Integrated in Hadoop-trunk-Commit #8755 (See https://builds.apache.org/job/Hadoop-trunk-Commit/8755/ ) HADOOP-12296 . when setnetgrent returns 0 in linux, exception should be (jlowe: rev b9d25c3ee2d20166d6a786c5a16cc001e249f61c) hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/security/JniBasedUnixGroupsNetgroupMapping.c hadoop-common-project/hadoop-common/CHANGES.txt
        Hide
        hudson Hudson added a comment -

        FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #638 (See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/638/)
        HADOOP-12296. when setnetgrent returns 0 in linux, exception should be (jlowe: rev b9d25c3ee2d20166d6a786c5a16cc001e249f61c)

        • hadoop-common-project/hadoop-common/CHANGES.txt
        • hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/security/JniBasedUnixGroupsNetgroupMapping.c
        Show
        hudson Hudson added a comment - FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #638 (See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/638/ ) HADOOP-12296 . when setnetgrent returns 0 in linux, exception should be (jlowe: rev b9d25c3ee2d20166d6a786c5a16cc001e249f61c) hadoop-common-project/hadoop-common/CHANGES.txt hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/security/JniBasedUnixGroupsNetgroupMapping.c
        Hide
        hudson Hudson added a comment -

        SUCCESS: Integrated in Hadoop-Yarn-trunk #1361 (See https://builds.apache.org/job/Hadoop-Yarn-trunk/1361/)
        HADOOP-12296. when setnetgrent returns 0 in linux, exception should be (jlowe: rev b9d25c3ee2d20166d6a786c5a16cc001e249f61c)

        • hadoop-common-project/hadoop-common/CHANGES.txt
        • hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/security/JniBasedUnixGroupsNetgroupMapping.c
        Show
        hudson Hudson added a comment - SUCCESS: Integrated in Hadoop-Yarn-trunk #1361 (See https://builds.apache.org/job/Hadoop-Yarn-trunk/1361/ ) HADOOP-12296 . when setnetgrent returns 0 in linux, exception should be (jlowe: rev b9d25c3ee2d20166d6a786c5a16cc001e249f61c) hadoop-common-project/hadoop-common/CHANGES.txt hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/security/JniBasedUnixGroupsNetgroupMapping.c
        Hide
        hudson Hudson added a comment -

        FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #627 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/627/)
        HADOOP-12296. when setnetgrent returns 0 in linux, exception should be (jlowe: rev b9d25c3ee2d20166d6a786c5a16cc001e249f61c)

        • hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/security/JniBasedUnixGroupsNetgroupMapping.c
        • hadoop-common-project/hadoop-common/CHANGES.txt
        Show
        hudson Hudson added a comment - FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #627 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/627/ ) HADOOP-12296 . when setnetgrent returns 0 in linux, exception should be (jlowe: rev b9d25c3ee2d20166d6a786c5a16cc001e249f61c) hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/security/JniBasedUnixGroupsNetgroupMapping.c hadoop-common-project/hadoop-common/CHANGES.txt
        Hide
        hudson Hudson added a comment -

        FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #571 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/571/)
        HADOOP-12296. when setnetgrent returns 0 in linux, exception should be (jlowe: rev b9d25c3ee2d20166d6a786c5a16cc001e249f61c)

        • hadoop-common-project/hadoop-common/CHANGES.txt
        • hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/security/JniBasedUnixGroupsNetgroupMapping.c
        Show
        hudson Hudson added a comment - FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #571 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/571/ ) HADOOP-12296 . when setnetgrent returns 0 in linux, exception should be (jlowe: rev b9d25c3ee2d20166d6a786c5a16cc001e249f61c) hadoop-common-project/hadoop-common/CHANGES.txt hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/security/JniBasedUnixGroupsNetgroupMapping.c
        Hide
        hudson Hudson added a comment -

        FAILURE: Integrated in Hadoop-Hdfs-trunk #2509 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/2509/)
        HADOOP-12296. when setnetgrent returns 0 in linux, exception should be (jlowe: rev b9d25c3ee2d20166d6a786c5a16cc001e249f61c)

        • hadoop-common-project/hadoop-common/CHANGES.txt
        • hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/security/JniBasedUnixGroupsNetgroupMapping.c
        Show
        hudson Hudson added a comment - FAILURE: Integrated in Hadoop-Hdfs-trunk #2509 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/2509/ ) HADOOP-12296 . when setnetgrent returns 0 in linux, exception should be (jlowe: rev b9d25c3ee2d20166d6a786c5a16cc001e249f61c) hadoop-common-project/hadoop-common/CHANGES.txt hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/security/JniBasedUnixGroupsNetgroupMapping.c
        Hide
        hudson Hudson added a comment -

        FAILURE: Integrated in Hadoop-Mapreduce-trunk #2569 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2569/)
        HADOOP-12296. when setnetgrent returns 0 in linux, exception should be (jlowe: rev b9d25c3ee2d20166d6a786c5a16cc001e249f61c)

        • hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/security/JniBasedUnixGroupsNetgroupMapping.c
        • hadoop-common-project/hadoop-common/CHANGES.txt
        Show
        hudson Hudson added a comment - FAILURE: Integrated in Hadoop-Mapreduce-trunk #2569 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2569/ ) HADOOP-12296 . when setnetgrent returns 0 in linux, exception should be (jlowe: rev b9d25c3ee2d20166d6a786c5a16cc001e249f61c) hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/security/JniBasedUnixGroupsNetgroupMapping.c hadoop-common-project/hadoop-common/CHANGES.txt
        Hide
        vinodkv Vinod Kumar Vavilapalli added a comment -

        Closing the JIRA as part of 2.7.3 release.

        Show
        vinodkv Vinod Kumar Vavilapalli added a comment - Closing the JIRA as part of 2.7.3 release.

          People

          • Assignee:
            lichangleo Chang Li
            Reporter:
            lichangleo Chang Li
          • Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development