You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 19, 2019. It is now read-only.
When deploying to a VPC where the storage-clients' resolver-setup cannot resolve the Gluster storage-server(s) by name, attempts to mount Gluster shares via systemd will silently fail.
Expected Behavior:
Reboot GlusterFS storage-client and all GlusterFS shares defined in /etc/fstab mount as defined.
Actual Behavior:
Reboot GlusterFS storage-client and all GlusterFS shares defined in /etc/fstab (may) silently fail
(Detailed) Steps to reproduce:
Deploy a GlusterFS storage-cluster
Deploy a GlusterFS storage-client
Add IP-based mount-definition in client's /etc/fstab file
Use mount -a to verify that fstab-defined mount-definition works as expected
Reboot storage-client
Find that fstab-defined mount is missing from list of active mounts and that system logs (journalctl -b 0) indicated that the mount-action successfully occurred .
(Optional) Fix recommendation:
Verified option:
Ensure that all members of the storage-cluster are resolveable
If DNS doesn't provide adequate resolver-response, add storage servers' self-advertised hostnames to storage client's /etc/hosts table
Reboot and verify the defined GlusterFS mounts are present
Alternate (Unverified) option:
Remove GlusterFS definitions from storage client's /etc/fstab file
Create a systemd mount service-definition for each GlusterFS share to mount to the client
Verify correctness of service-definition by executing systemctl start <MOUNT_PATH>.mount` and ensure that targeted mount-point is active
The text was updated successfully, but these errors were encountered:
Problem Description:
When deploying to a VPC where the storage-clients' resolver-setup cannot resolve the Gluster storage-server(s) by name, attempts to mount Gluster shares via systemd will silently fail.
Expected Behavior:
Reboot GlusterFS storage-client and all GlusterFS shares defined in
/etc/fstab
mount as defined.Actual Behavior:
Reboot GlusterFS storage-client and all GlusterFS shares defined in
/etc/fstab
(may) silently fail(Detailed) Steps to reproduce:
/etc/fstab
filemount -a
to verify thatfstab
-defined mount-definition works as expectedfstab
-defined mount is missing from list of active mounts and that system logs (journalctl -b 0
) indicated that the mount-action successfully occurred .(Optional) Fix recommendation:
Verified option:
/etc/hosts
tableAlternate (Unverified) option:
/etc/fstab
filemount
service-definition for each GlusterFS share to mount to the clientsystemctl start
<MOUNT_PATH>.mount` and ensure that targeted mount-point is activeThe text was updated successfully, but these errors were encountered: