Bug 1283144
Summary: | glusterfs does not register with rpcbind on restart | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Niels de Vos <ndevos> |
Component: | packaging | Assignee: | Niels de Vos <ndevos> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.6.7 | CC: | amukherj, devops, kaushal, nlevinki, rabhat, vbellur |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.6.7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1282915 | Environment: | |
Last Closed: | 2015-12-02 08:25:37 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: | 1282915 | ||
Bug Blocks: | 1267567 |
Description
Niels de Vos
2015-11-18 11:28:21 UTC
REVIEW: http://review.gluster.org/12641 (glusterd.service: Ensure rpcbind is started before glusterd) posted (#1) for review on release-3.6 by Niels de Vos (ndevos) COMMIT: http://review.gluster.org/12641 committed in release-3.6 by Raghavendra Bhat (raghavendra) ------ commit 73527a122ceb50c47812f4d3f50faf0172697d6f Author: Niels de Vos <ndevos> Date: Wed Nov 18 12:28:50 2015 +0100 glusterd.service: Ensure rpcbind is started before glusterd Having the rpcbind.service under the `After` option only ensures that glusterd.service is started after rpcbind.service if both are enabled/started at the same time. It doesn't ensure that starting glusterd.service will start rpcbind.service. The systemd.unit(5) man page suggests to use both the `Requires` and `After` options to ensure that rpcbind is started before glusterd, whenever glusterd is started. Cherry picked from commit 23440a73bc348bbc3bb43ec397f0639ee45865fc: > BUG: 1282915 > Change-Id: Iee69965486be08711299aba235f7b00c3e2fe7e9 > Signed-off-by: Kaushal M <kaushal> > Reviewed-on: http://review.gluster.org/12605 > Reviewed-by: Atin Mukherjee <amukherj> > Reviewed-by: Anand Nekkunti <anekkunt> > Tested-by: Gluster Build System <jenkins.com> > Tested-by: NetBSD Build System <jenkins.org> Change-Id: Iee69965486be08711299aba235f7b00c3e2fe7e9 BUG: 1283144 Signed-off-by: Niels de Vos <ndevos> Reviewed-on: http://review.gluster.org/12641 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Atin Mukherjee <amukherj> Reviewed-by: Raghavendra Bhat <raghavendra> This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.6.7, please open a new bug report. glusterfs-3.6.7 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://www.gluster.org/pipermail/gluster-devel/2015-December/047260.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |