Bug 1406165 (hadoop-hdfs_network-online)

Summary: hadoop-namenode listens on loopback interface
Product: [Fedora] Fedora Reporter: Christopher Tubbs <ctubbsii>
Component: hadoopAssignee: Christopher Tubbs <ctubbsii>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: besser82, coolsvap, matt, milleruntime, moceap, rebus
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-27 23:13:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1119787    

Description Christopher Tubbs 2016-12-19 21:20:15 UTC
Description of problem:
When the hadoop-namenode service is configured to start at boot (systemctl enable hadoop-namenode), it incorrectly binds to the loopback interface instead of the public interface. This is probably because the systemd unit file does not wait on the network interfaces to start up fully.

Version-Release number of selected component (if applicable):
hadoop-hdfs-2.4.1-24.fc25.noarch

How reproducible:
Almost always, after a reboot.

Steps to Reproduce:
1. systemctl enable hadoop-namenode
2. reboot
3. netstat -tlnp

Actual results:
the namenode is bound to 127.0.0.2

Expected results:
it should be bound to the IP address for the primary NIC

Additional info:
The namenode can be restarted after the system is fully up, and then it will correctly bind to the right interface.

Comment 1 Christopher Tubbs 2016-12-19 21:20:44 UTC
It could also bind to 0.0.0.0 instead, which would make sense as a default.

Comment 2 Michal Ambroz 2017-11-06 20:16:15 UTC
I guess this could very well be race condition with the network manager starting the network. During this race condition on a machine with more network cards the resolv of hostname could result in 127.0.0.2. 
Can you try changing the hadoop-hdfs.service from network.target to depend on network-online.target ?

Seems to affect rawhide / fedora 27 as well.

Comment 3 Ben Cotton 2018-11-27 17:10:22 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2019-10-31 18:57:30 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2019-11-27 23:13:16 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.