Bug 1553372

Summary: ganglia: ganglia-gmond should use network-online.target
Product: [Fedora] Fedora EPEL Reporter: Stefan Dietrich <stefan.dietrich>
Component: gangliaAssignee: Nick <nick>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel7CC: athanasios.kanaris, jose.p.oliveira.oss, nick
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ganglia-3.7.2-33.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-23 22:50:43 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:

Description Stefan Dietrich 2018-03-08 18:26:22 UTC
Description of problem:
The ganglia gmond does not start under certain conditions.
"systemctl start gmond" will just block and not return, if it is executed not in multi-user.target:

[Unit]
Description=Ganglia Monitoring Daemon
After=multi-user.target

The gmond.service unit file should use network-online.target in order to avoid this situation:

[Unit]
Description=Ganglia Monitoring Daemon
After=network-online.target

This is also the default configuration of the unit file from upstream:
https://github.com/ganglia/monitor-core/blob/master/gmond/gmond.service.in

Version-Release number of selected component (if applicable):
ganglia-gmond-3.7.2-2.el7.x86_64

How reproducible:
Try to start gmond while not in multi-user.target, e.g. during operating system provisioning

Steps to Reproduce:
1. Install ganglia & ganglia-gmond
2. Run "systemctl start gmond" while not yet entered multi-user.target

Actual results:
systemctl start gmond will block and not return

Expected results:
gmond should be started

Additional info:
Problem encountered during deployment of new os installation.

Comment 1 Athanasios Kanaris 2019-02-22 16:15:18 UTC
Hello,

Is there an update on this? This is creating an issue with our kickstart procedure as well.

Comment 2 Fedora Update System 2020-10-08 22:13:55 UTC
FEDORA-EPEL-2020-fee165c6a2 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-fee165c6a2

Comment 3 Fedora Update System 2020-10-09 00:02:48 UTC
FEDORA-EPEL-2020-fee165c6a2 has been pushed to the Fedora EPEL 7 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-fee165c6a2

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2020-10-23 22:50:43 UTC
FEDORA-EPEL-2020-fee165c6a2 has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, please make note of it in this bug report.