Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 26EE09FA7 for ; Wed, 23 May 2012 13:34:42 +0000 (UTC) Received: (qmail 11816 invoked by uid 500); 23 May 2012 13:34:41 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 11732 invoked by uid 500); 23 May 2012 13:34:41 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 11712 invoked by uid 99); 23 May 2012 13:34:41 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 May 2012 13:34:41 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id DDC04142826 for ; Wed, 23 May 2012 13:34:40 +0000 (UTC) Date: Wed, 23 May 2012 13:34:40 +0000 (UTC) From: "Daryn Sharp (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <977026838.11598.1337780080912.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1613863787.16933.1337380986722.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HADOOP-8414) Address problems related to localhost resolving to 127.0.0.1 on Windows MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281600#comment-13281600 ] Daryn Sharp commented on HADOOP-8414: ------------------------------------- The {{HarFileSystem}} change is probably worthy of its own jira now since it's generally useful and should be able to stand alone w/o the other changes in this jira. This jira would then just depend on the new one since it indirectly addresses issues for this jira. I forgot to mention that if the discrepancy with window's resolution of {{localhost}} is likely to break host-based tokens ({{hadoop.security.token.service.use_ip=false}}). We'll need to be sure to test host-based tokens if the discrepancy is real and can't be fixed. > Address problems related to localhost resolving to 127.0.0.1 on Windows > ----------------------------------------------------------------------- > > Key: HADOOP-8414 > URL: https://issues.apache.org/jira/browse/HADOOP-8414 > Project: Hadoop Common > Issue Type: Bug > Components: fs, test > Affects Versions: 1.0.0 > Reporter: Ivan Mitic > Assignee: Ivan Mitic > Attachments: HADOOP-8414-branch-1-win.patch, HADOOP-8414-branch-1-win.patch > > > Localhost resolves to 127.0.0.1 on Windows and that causes the following tests to fail: > - TestHarFileSystem > - TestCLI > - TestSaslRPC > This Jira tracks fixing these tests and other possible places that have similar issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira