[HDFS-4043] Namenode Kerberos Login does not use proper hostname for host qualified hdfs principal name.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0-alpha, 2.0.1-alpha, 2.0.2-alpha, 2.0.3-alpha, 3.4.0, 3.3.5
• Fix Version/s: 3.4.0, 3.3.5
• Component/s: security
• Labels: pull-request-available

Environment

CDH4U1 on Ubuntu 12.04

• Hadoop Flags: Reviewed
• Assignee: Steve Vaughan
• Reporter: Ahad Rana
• Created: 12/Oct/12 00:43
• Updated: 22/Aug/22 21:35
• Resolved: 22/Aug/22 21:35

Description

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.

Issue Links

• is a child of: HADOOP-18396 Issues running in dynamic / managed environments
• links to: GitHub Pull Request #4693
• links to: GitHub Pull Request #4785