[
https://issues.apache.org/jira/browse/HADOOP-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281752#comment-13281752
]
Ivan Mitic commented on HADOOP-8414:
------------------------------------
Thanks Daryn, some answers/comments inline.
Could you please do the same testing with InetAddress.getByName("localhost") to
ensure that something else isn't botching the hostname to 127.0.0.1?
@Daryn: Same result as with null.
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
@Daryn: Sure.
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.
@Daryn: I see, thanks for bringing this up. Do you maybe know of a test that
can catch this?
> 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
