[
https://issues.apache.org/jira/browse/HADOOP-6947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909644#action_12909644
]
Hadoop QA commented on HADOOP-6947:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12454185/hadoop-6947.txt
against trunk revision 995285.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 5 new or modified tests.
-1 javadoc. The javadoc tool appears to have generated 1 warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
+1 system tests framework. The patch passed system tests framework compile.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/681/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/681/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/681/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/681/console
This message is automatically generated.
> Kerberos relogin should set refreshKrb5Config to true
> -----------------------------------------------------
>
> Key: HADOOP-6947
> URL: https://issues.apache.org/jira/browse/HADOOP-6947
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 0.22.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: hadoop-6947-branch20.txt, hadoop-6947.txt
>
>
> In working on securing a daemon that uses two different principals from
> different threads, I found that I wasn't able to login from a second keytab
> after I'd logged in from the first. This is because we don't set the
> refreshKrb5Config in the Configuration for the Krb5LoginModule - hence it
> won't switch over to the correct keytab file if it's different than the first.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
