[KAFKA-4765] org.apache.kafka.clients.producer.KafkaProducerTest#testConstructorFailureCloseResource and Similar Tests are Failing on some Systems (127.0.53.53 Collision Warning)

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.10.1.1
• Fix Version/s: 0.11.0.0
• Component/s: unit tests
• Environment: All DNS environments that properly forward 127.0.53.53
• Assignee: Unassigned
• Reporter: Armin Braun
• Created: 15/Feb/17 07:55
• Updated: 16/Feb/17 14:40
• Resolved: 16/Feb/17 14:39

Description

The test

org.apache.kafka.clients.producer.KafkaProducerTest#testConstructorFailureCloseResource

fails on some systems because this below snippet from

org.apache.kafka.clients.ClientUtils#parseAndValidateAddresses

                    InetSocketAddress address = new InetSocketAddress(host, port);

                    if (address.isUnresolved()) {
                        log.warn("Removing server {} from {} as DNS resolution failed for {}", url, CommonClientConfigs.BOOTSTRAP_SERVERS_CONFIG, host);
                    } else {
                        addresses.add(address);
                    }

will add the address some.invalid.hostname.foo.bar to the addresses list without error since it is resolved to 127.0.53.53 to indicate potential future collision of the .bar tld.
The same issue applies to a few other test cases that try to intentionally run into broken hostnames.

This can (and should) be fixed by using broken hostname examples that do not collide. I would suggest just putting a ".local" suffix on all that are currently affected by this.

Issue Links

• links to: GitHub Pull Request #2552