Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Fri, 12 Oct 2012 00:39:03 +0000 (UTC)
From: "Ahad Rana (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <995140126.34180.1350002343651.JavaMail.jiratomcat@arcas>
Subject: [jira] [Created] (HADOOP-8919) Namenode Kerberos Login does not use
 proper hostname for host qualified hdfs principal name.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Ahad Rana created HADOOP-8919:
---------------------------------

             Summary: Namenode Kerberos Login does not use proper hostname for host qualified hdfs principal name.
                 Key: HADOOP-8919
                 URL: https://issues.apache.org/jira/browse/HADOOP-8919
             Project: Hadoop Common
          Issue Type: Bug
          Components: security
    Affects Versions: 2.0.2-alpha, 2.0.1-alpha, 2.0.0-alpha, 2.0.3-alpha
         Environment: CDH4U1 using Kerberos on Ubuntu 12.01
            Reporter: Ahad Rana


The Namenode uses the loginAsNameNodeUser method in NameNode.java to login using the hdfs principal. This method in turn invokes SecurityUtil.login with a hostname (last parameter) obtained via a call to InetAddress.getHostName. This call does not always return the fully qualified host name, and thus causes the namenode to login to fail due to kerberos's inability to find a matching hdfs principal in the hdfs.keytab file. Instead it should use InetAddress.getCanonicalHostName. This is consistent with what is used internally by SecurityUtil.java to login in other services, such as the DataNode. 

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