Bug 1317559
Summary: | Glusterfs mounts in fstab are not mounted at boot | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Mathieu MD <mathieu+redhat> |
Component: | glusterd | Assignee: | bugs <bugs> |
Status: | CLOSED EOL | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.7.8 | CC: | brian, bugs, hvjunk, ish1301, mliyazud, olim, wfdata |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-03-08 10:56:10 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
Mathieu MD
2016-03-14 14:45:14 UTC
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release. This is still valid for Gluster 3.10 mount needs to either retry, or the glusterfsd needs to only finish once a "gluster volume list" is functional with the glusterfsd talking to the other in the cluster. This is also easy to recreate during bootstrapping of the cluster There should some option to delayed start of GlusterFS mount or auto retry to mount if it fails |