Bug 954190
Summary: | /etc/init.d/glusterfsd missing from upstream git compiled rpms | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Justin Clift <jclift> |
Component: | build | Assignee: | Kaleb KEITHLEY <kkeithle> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | mainline | CC: | gluster-bugs, kwade |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-06-20 13:17:17 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
Justin Clift
2013-04-21 18:42:59 UTC
upstream glusterfs.org rpms have historically not provided a /etc/init.d/glusterfsd (or /var/lib/systemd/system/glusterfsd.service). Nor have downstream RHS rpms either, fwiw. upstream fedoraproject.org rpms do have a /etc/init.d/glusterfsd (or /var/lib/systemd/system/glusterfsd.service) But see http://review.gluster.org/5179 (release-3.4) and http://review.gluster.org/5230 (master) and feel free to review. In particular see the commit comment about "still considering whether to add fedora glusterfsd.{init,service} files to glusterfs or remove them from fedora." *** This bug has been marked as a duplicate of bug 950083 *** Understood. I don't have a preference either way about the inclusion of glusterfsd in init.d (and maybe systemd equivalent?). The problem I'm referring to in this bug is the warning message here: "error reading information on service glusterfsd: No such file or directory" Something is creating that warning, which we should fix. Whether it's by including the glusterfsd it's referring to, or just nuking the warning, I don't have a preference for. My Gluster installation seems to be working fine (regardless of underlying OS), even when this warning happens... so maybe we should just kill the warning? |