Bug 1105283
Summary: | Failure to start geo-replication. | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | vnosov <vnosov> |
Component: | geo-replication | Assignee: | Aravinda VK <avishwan> |
Status: | CLOSED EOL | QA Contact: | |
Severity: | urgent | Docs Contact: | |
Priority: | medium | ||
Version: | 3.5.0 | CC: | avishwan, bugs, david.c.gibbons, jbyers, mselvaga |
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: | 2016-06-17 16:23:41 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
vnosov
2014-06-05 18:50:55 UTC
Version 3.5.1beta has the same problem. The GlusterFS installation was done on Centos by using glusterfs-3.5.1.tar or glusterfs-3.5.1beta.tar. GlusterFS configure summary =========================== FUSE client : yes Infiniband verbs : no epoll IO multiplex : yes argp-standalone : no fusermount : yes readline : yes georeplication : yes Linux-AIO : yes Enable Debug : no systemtap : no Block Device xlator : no glupy : no Use syslog : yes XML output : yes QEMU Block formats : yes Encryption xlator : yes It seems that the installation has problem to run geo-replication because scripts do not have valid path for gluster, glusterfs and gsyncd. For example: attempt to execute /nonexistent/gsyncd fails. After setting symbolic links geo-replication started successfully. Installation from the tar file has to do it itself and set valid path for gluster, glusterfs and qsyncd. looks like pem key distribution failed. Was not able duplicate this bug with version 3.6.2. This bug is getting closed because the 3.5 is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release. |