You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2013/02/19 17:23:12 UTC

[jira] [Commented] (HADOOP-9317) User cannot specify a kerberos keytab for commands

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

Hadoop QA commented on HADOOP-9317:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12569954/HADOOP-9317.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/2201//console

This message is automatically generated.
                
> User cannot specify a kerberos keytab for commands
> --------------------------------------------------
>
>                 Key: HADOOP-9317
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9317
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Critical
>         Attachments: HADOOP-9317.branch-23.patch, HADOOP-9317.patch
>
>
> {{UserGroupInformation}} only allows kerberos users to be logged in via the ticket cache when running hadoop commands.  {{UGI}} allows a keytab to be used, but it's only exposed programatically.  This forces keytab-based users running hadoop commands to periodically issue a kinit from the keytab.  A race condition exists during the kinit when the ticket cache is deleted and re-created.  Hadoop commands will fail when the ticket cache does not momentarily exist.

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