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 "Arpit Gupta (JIRA)" <ji...@apache.org> on 2012/10/04 02:47:08 UTC
[jira] [Created] (HADOOP-8878) uppercase hostname causes hadoop dfs
calls with webhdfs filesystem to fail
Arpit Gupta created HADOOP-8878:
-----------------------------------
Summary: uppercase hostname causes hadoop dfs calls with webhdfs filesystem to fail
Key: HADOOP-8878
URL: https://issues.apache.org/jira/browse/HADOOP-8878
Project: Hadoop Common
Issue Type: Bug
Affects Versions: 1.0.3, 1.1.0, 1.2.0
Reporter: Arpit Gupta
Assignee: Arpit Gupta
This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
hadoop dfs -ls webhdfs://NN:PORT/PATH
the above command failed because delegation token retrieval failed.
Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Updated] (HADOOP-8878) uppercase hostname causes hadoop dfs
calls with webhdfs filesystem to fail when security is on
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Gupta updated HADOOP-8878:
--------------------------------
Summary: uppercase hostname causes hadoop dfs calls with webhdfs filesystem to fail when security is on (was: uppercase hostname causes hadoop dfs calls with webhdfs filesystem to fail)
> uppercase hostname causes hadoop dfs calls with webhdfs filesystem to fail when security is on
> ----------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Updated] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Gupta updated HADOOP-8878:
--------------------------------
Summary: uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on (was: uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem to fail when security is on)
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Updated] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Gupta updated HADOOP-8878:
--------------------------------
Attachment: HADOOP-8878.branch-1.patch
branch-1 patch where i have created a method in KerberosUtil to get service principal. Let me know this approach looks good and will do the same for trunk.
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Commented] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470660#comment-13470660 ]
Hadoop QA commented on HADOOP-8878:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12548033/HADOOP-8878.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in hadoop-common-project/hadoop-auth.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/1567//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/1567//console
This message is automatically generated.
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Updated] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Gupta updated HADOOP-8878:
--------------------------------
Attachment: HADOOP-8878.branch-1.patch
patch for branch-1 with local in the toLowerCase.
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Updated] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Gupta updated HADOOP-8878:
--------------------------------
Status: Open (was: Patch Available)
canceling the patch to adress Steve's comments.
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Commented] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Daryn Sharp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470464#comment-13470464 ]
Daryn Sharp commented on HADOOP-8878:
-------------------------------------
+1 Ok.
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Commented] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469491#comment-13469491 ]
Arpit Gupta commented on HADOOP-8878:
-------------------------------------
This would also impact fsck as it goes through the same code path.
@Dayrn i will take a look and see what can be done to add the ability to write a test for it.
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Updated] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Gupta updated HADOOP-8878:
--------------------------------
Status: Patch Available (was: Open)
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch, HADOOP-8878.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Updated] (HADOOP-8878) uppercase hostname causes hadoop dfs
calls with webhdfs filesystem to fail when security is on
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Gupta updated HADOOP-8878:
--------------------------------
Status: Patch Available (was: Open)
> uppercase hostname causes hadoop dfs calls with webhdfs filesystem to fail when security is on
> ----------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Commented] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474134#comment-13474134 ]
Hudson commented on HADOOP-8878:
--------------------------------
Integrated in Hadoop-Mapreduce-trunk #1223 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1223/])
HADOOP-8878. Uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on. Contributed by Arpit Gupta. (Revision 1396922)
Result = FAILURE
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1396922
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-auth/src/main/java/org/apache/hadoop/security/authentication/client/KerberosAuthenticator.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-auth/src/main/java/org/apache/hadoop/security/authentication/util/KerberosUtil.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/util/TestKerberosUtil.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Fix For: 1.2.0, 2.0.3-alpha
>
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch, HADOOP-8878.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Updated] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Gupta updated HADOOP-8878:
--------------------------------
Attachment: HADOOP-8878.patch
patch for trunk.
Instead of using SecuirtyUtil.getLocalHostname add a similar method in KerberosUtil as hadoop-auth depending on hadoop-common creates a circular dependency.
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Updated] (HADOOP-8878) uppercase hostname causes hadoop dfs
calls with webhdfs filesystem to fail
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Gupta updated HADOOP-8878:
--------------------------------
Attachment: HADOOP-8878.branch-1.patch
patch for branch-1
> uppercase hostname causes hadoop dfs calls with webhdfs filesystem to fail
> --------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Updated] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem to fail when security is on
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Gupta updated HADOOP-8878:
--------------------------------
Summary: uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem to fail when security is on (was: uppercase hostname causes hadoop dfs calls with webhdfs filesystem to fail when security is on)
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem to fail when security is on
> -------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Updated] (HADOOP-8878) uppercase hostname causes hadoop dfs
calls with webhdfs filesystem to fail when security is on
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Gupta updated HADOOP-8878:
--------------------------------
Attachment: HADOOP-8878.patch
patch for trunk
> uppercase hostname causes hadoop dfs calls with webhdfs filesystem to fail when security is on
> ----------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Updated] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Suresh Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suresh Srinivas updated HADOOP-8878:
------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.3-alpha
1.2.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
+1 for the patch. I committed it to trunk , branch-2 and branch-1. Thank you Arpit.
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Fix For: 1.2.0, 2.0.3-alpha
>
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch, HADOOP-8878.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Commented] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473116#comment-13473116 ]
Steve Loughran commented on HADOOP-8878:
----------------------------------------
+1; thanks for the i18n tweak!
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch, HADOOP-8878.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Commented] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472610#comment-13472610 ]
Hadoop QA commented on HADOOP-8878:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12548435/HADOOP-8878.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in hadoop-common-project/hadoop-auth.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/1590//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/1590//console
This message is automatically generated.
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch, HADOOP-8878.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Commented] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473915#comment-13473915 ]
Hudson commented on HADOOP-8878:
--------------------------------
Integrated in Hadoop-Common-trunk-Commit #2844 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2844/])
HADOOP-8878. Uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on. Contributed by Arpit Gupta. (Revision 1396922)
Result = SUCCESS
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1396922
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-auth/src/main/java/org/apache/hadoop/security/authentication/client/KerberosAuthenticator.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-auth/src/main/java/org/apache/hadoop/security/authentication/util/KerberosUtil.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/util/TestKerberosUtil.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Fix For: 1.2.0, 2.0.3-alpha
>
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch, HADOOP-8878.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Commented] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470472#comment-13470472 ]
Arpit Gupta commented on HADOOP-8878:
-------------------------------------
Will work on a trunk patch that follows the same approach.
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Commented] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem to fail when security is on
Posted by "Daryn Sharp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469393#comment-13469393 ]
Daryn Sharp commented on HADOOP-8878:
-------------------------------------
+1 Although I'd suggest breaking out some of the code into a new method to allow a unit test to be written.
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem to fail when security is on
> -------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Commented] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472245#comment-13472245 ]
Steve Loughran commented on HADOOP-8878:
----------------------------------------
-1: needs to use {{String.toLowerCase(Locale.EN_US)}} to work reliably round the world. You don't want to field unreplicable support cases from Turkey.
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Commented] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469497#comment-13469497 ]
Owen O'Malley commented on HADOOP-8878:
---------------------------------------
Yeah, I agree that it would be good to make a separate function.
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Commented] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472613#comment-13472613 ]
Arpit Gupta commented on HADOOP-8878:
-------------------------------------
test patch output for branch-1
{code}
[exec]
[exec] -1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 2 new or modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings.
[exec]
[exec] -1 findbugs. The patch appears to introduce 9 new Findbugs (version 1.3.9) warnings.
[exec]
[exec]
[exec]
[exec]
[exec] ======================================================================
[exec] ======================================================================
[exec] Finished build.
[exec] ======================================================================
[exec] ======================================================================
[exec]
[exec]
{code}
findbugs warnings are not related to this patch.
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch, HADOOP-8878.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Commented] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470389#comment-13470389 ]
Arpit Gupta commented on HADOOP-8878:
-------------------------------------
@Dayrn
I just replicated what we do in SecurityUtil.replacePattern for the same
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Commented] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469492#comment-13469492 ]
Arpit Gupta commented on HADOOP-8878:
-------------------------------------
oops meant Daryn :)
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Updated] (HADOOP-8878) uppercase hostname causes hadoop dfs
calls with webhdfs filesystem to fail when security is on
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Gupta updated HADOOP-8878:
--------------------------------
Affects Version/s: 3.0.0
> uppercase hostname causes hadoop dfs calls with webhdfs filesystem to fail when security is on
> ----------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Commented] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Matt Foley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501490#comment-13501490 ]
Matt Foley commented on HADOOP-8878:
------------------------------------
included in branch-1.1
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Fix For: 1.1.1, 2.0.3-alpha
>
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch, HADOOP-8878.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Updated] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Gupta updated HADOOP-8878:
--------------------------------
Status: Patch Available (was: Open)
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Commented] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474118#comment-13474118 ]
Hudson commented on HADOOP-8878:
--------------------------------
Integrated in Hadoop-Hdfs-trunk #1192 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1192/])
HADOOP-8878. Uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on. Contributed by Arpit Gupta. (Revision 1396922)
Result = SUCCESS
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1396922
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-auth/src/main/java/org/apache/hadoop/security/authentication/client/KerberosAuthenticator.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-auth/src/main/java/org/apache/hadoop/security/authentication/util/KerberosUtil.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/util/TestKerberosUtil.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Fix For: 1.2.0, 2.0.3-alpha
>
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch, HADOOP-8878.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Commented] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Daryn Sharp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470301#comment-13470301 ]
Daryn Sharp commented on HADOOP-8878:
-------------------------------------
Looks good, but I'm curious when it would be legitimate to pass null or an empty string for the host?
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Commented] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem to fail when security is on
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469077#comment-13469077 ]
Hadoop QA commented on HADOOP-8878:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12547655/HADOOP-8878.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:red}-1 tests included{color}. 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.
{color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in hadoop-common-project/hadoop-auth.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/1555//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/1555//console
This message is automatically generated.
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem to fail when security is on
> -------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Updated] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Matt Foley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Foley updated HADOOP-8878:
-------------------------------
Fix Version/s: (was: 1.2.0)
1.1.1
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Fix For: 1.1.1, 2.0.3-alpha
>
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch, HADOOP-8878.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Updated] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Gupta updated HADOOP-8878:
--------------------------------
Attachment: HADOOP-8878.patch
patch for trunk which is using LOCALE.US in toLowerCase
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch, HADOOP-8878.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Commented] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473919#comment-13473919 ]
Hudson commented on HADOOP-8878:
--------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #2906 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2906/])
HADOOP-8878. Uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on. Contributed by Arpit Gupta. (Revision 1396922)
Result = SUCCESS
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1396922
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-auth/src/main/java/org/apache/hadoop/security/authentication/client/KerberosAuthenticator.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-auth/src/main/java/org/apache/hadoop/security/authentication/util/KerberosUtil.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/util/TestKerberosUtil.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Fix For: 1.2.0, 2.0.3-alpha
>
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch, HADOOP-8878.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Updated] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Gupta updated HADOOP-8878:
--------------------------------
Status: Open (was: Patch Available)
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Commented] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469779#comment-13469779 ]
Arpit Gupta commented on HADOOP-8878:
-------------------------------------
Here is the output of test patch for branch 1
{code}
[exec] -1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 2 new or modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings.
[exec]
[exec] -1 findbugs. The patch appears to introduce 9 new Findbugs (version 1.3.9) warnings.
[exec]
[exec]
{code}
Findbugs warnings are unrelated to this patch.
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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
[jira] [Commented] (HADOOP-8878) uppercase namenode hostname causes
hadoop dfs calls with webhdfs filesystem and fsck to fail when security is
on
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473911#comment-13473911 ]
Hudson commented on HADOOP-8878:
--------------------------------
Integrated in Hadoop-Mapreduce-trunk-Commit #2868 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2868/])
HADOOP-8878. Uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on. Contributed by Arpit Gupta. (Revision 1396922)
Result = FAILURE
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1396922
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-auth/src/main/java/org/apache/hadoop/security/authentication/client/KerberosAuthenticator.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-auth/src/main/java/org/apache/hadoop/security/authentication/util/KerberosUtil.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/util/TestKerberosUtil.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8878
> URL: https://issues.apache.org/jira/browse/HADOOP-8878
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Fix For: 1.2.0, 2.0.3-alpha
>
> Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.patch, HADOOP-8878.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.
--
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