Bug 1344551
Summary: | Automount fails because /sbin/mount.glusterfs does not accept the -s option | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Niels de Vos <ndevos> |
Component: | fuse | Assignee: | Niels de Vos <ndevos> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.7.12 | CC: | bugs |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.7.13 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1340936 | Environment: | |
Last Closed: | 2016-07-20 13:55: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: | 1340936 | ||
Bug Blocks: | 1350804 |
Description
Niels de Vos
2016-06-10 02:39:23 UTC
REVIEW: http://review.gluster.org/14686 (fuse: accept the -s option to allow automounting) posted (#1) for review on release-3.7 by Niels de Vos (ndevos) REVIEW: http://review.gluster.org/14686 (fuse: accept the -s option to allow automounting) posted (#2) for review on release-3.7 by Niels de Vos (ndevos) COMMIT: http://review.gluster.org/14686 committed in release-3.7 by Niels de Vos (ndevos) ------ commit 3aed8bbefe0078eca80dd3a53f005e7a94281424 Author: Niels de Vos <ndevos> Date: Mon May 30 21:01:29 2016 +0200 fuse: accept the -s option to allow automounting autofs passes the -s option when mounting. All /sbin/mount.<fs> helpers accept this, except mount.glusterfs. Because the helper fails when -s is passed accessing the mountpoint through autofs gives the following error: $ ls /lan/storage.lan.example.net/repos ls: cannot open directory /lan/storage.lan.example.net/repos: Too many levels of symbolic links Cherry picked from commit c8da5669a15ed6944cceb9d003789ff333754bff: > BUG: 1340936 > Change-Id: I84755cdac59e630618cb745c0eb3228cc1e93a1a > Signed-off-by: Niels de Vos <ndevos> > Reviewed-on: http://review.gluster.org/14559 > NetBSD-regression: NetBSD Build System <jenkins.org> > CentOS-regression: Gluster Build System <jenkins.com> > Smoke: Gluster Build System <jenkins.com> > Reviewed-by: Oleksandr Natalenko <oleksandr> Change-Id: I84755cdac59e630618cb745c0eb3228cc1e93a1a BUG: 1344551 Signed-off-by: Niels de Vos <ndevos> Tested-by: Kaveh Minooie <kminooie> Reviewed-on: http://review.gluster.org/14686 Smoke: Gluster Build System <jenkins.org> Reviewed-by: Oleksandr Natalenko <oleksandr> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> 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.7.13, please open a new bug report. glusterfs-3.7.13 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] https://www.gluster.org/pipermail/gluster-users/2016-July/027604.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |