NameNode binds to wrong IP address in MiniDFS
Description
Activity
Show:
Antonios Kouzoupis April 12, 2019 at 2:04 PM
UPDATE
Some tests fail because they explicitly assert NameNode IP is not 0.0.0.0 So, we revert back to 127.0.0.1. In your '/etc/hosts', your hostname should resolve to 127.0.0.1
In the end, this Jira will just change the use of hostname with FQDN instead. This change is not necessary as there is code which checks for both.
When a NameNode is created with MiniDFS for tests, it binds to 'localhost' and '127.0.0.1' This, depending on '/etc/hosts', might fail the tests for Hops TLS.
When Hops TLS is enabled and the user making the RPC call is a superuser, it authenticates him by doing a reverse DNS lookup for the incoming IP. The FQDN/hostname of the remote IP should match the CN of the X.509 certificate. This is not always the case when a service binds to 127.0.0.1/localhost.