[
https://issues.apache.org/jira/browse/ZOOKEEPER-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17296548#comment-17296548
]
Damien Diederen commented on ZOOKEEPER-4197:
--------------------------------------------
Hi [~amichai],
bq. This fails on systems, such as several Linux distributions, where that
resolves to "localhost.localdomain".
Could you add an example of one such Linux distribution?
Note that hardcoding {{localhost}}, per se, seems fine to me; [RFC
6761|https://tools.ietf.org/html/rfc6761] says:
bq. Users may assume that IPv4 and IPv6 address queries for localhost names
will always resolve to the respective IP loopback address.
But expecting the result of a reverse lookup to be {{localhost}} doesn't seem
to be a good idea, indeed.
> Various tests fail on localhost.localdomain
> -------------------------------------------
>
> Key: ZOOKEEPER-4197
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4197
> Project: ZooKeeper
> Issue Type: Bug
> Components: tests
> Affects Versions: 3.6.3
> Reporter: Amichai Rothman
> Priority: Major
>
> Various tests have "localhost" hardcoded and/or do a reverse lookup on
> 127.0.0.1 and expect it to be "localhost". This fails on systems, such as
> several Linux distributions, where that resolves to "localhost.localdomain".
> Tests should be fixed so the build can succeed on all such systems, even if
> localhost is named localhost.localdomain.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)