[Bugs] [Bug 1147252] New: Pacemaker OCF volume Resource Agent fails when bricks are in different domain to the system hostname.
bugzilla at redhat.com
bugzilla at redhat.com
Sun Sep 28 12:45:24 UTC 2014
https://bugzilla.redhat.com/show_bug.cgi?id=1147252
Bug ID: 1147252
Summary: Pacemaker OCF volume Resource Agent fails when bricks
are in different domain to the system hostname.
Product: GlusterFS
Version: mainline
Component: scripts
Keywords: EasyFix, Patch, Triaged
Severity: medium
Assignee: gluster-bugs at redhat.com
Reporter: ndevos at redhat.com
CC: bugs at gluster.org, bugzilla at stevenhale.co.uk,
gluster-bugs at redhat.com
Blocks: 1130763
+++ This bug was initially created as a clone of Bug #1130763 +++
+++ +++
+++ This bug is used to make the change in the master branch. +++
+++ +++
Description of problem:
I'm setting up a four-node cluster using PCS/Pacemaker/Corosync on CentOS7. I
have installed glusterfs-resource-agents.noarch 0:3.5.2-1.el7 from the main
GlusterFS yum repository.
As is common when setting up a cluster, I am using a storage network separate
from the back channel network. I have added entries to my local nameserver to
reflect these networks. The hostnames are as follows:
node?.bcn
node?.sn
When trying to start a volume using the
"/usr/lib/ocf/resource.d/glusterfs/volume" resource, the volume fails to start
because the script does not recognise that the bricks are in a different domain
to the system hostname.
I have fixed this bug and will attach a patch file to this report. The fix
simply involves editing a regular expression and a file path.
I also had to update the volume path to reflect that volume information is now
stored in /var/lib/ rather than /etc.
Version-Release number of selected component (if applicable):
glusterfs-resource-agents.noarch 0:3.5.2-1.el7
How reproducible:
Always
Steps to Reproduce:
1. Create a GlusterFS volume where the bricks are in a different domain to the
central system hostname.
2. Try to start the volume using the OCF volume resource agent for Pacemaker.
Actual results:
The volume does not start. The script always thinks the volume is already
running.
Expected results:
The volume should start normally.
Additional info:
Patchfile attached to bug 1130763 as attachment #927478.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1130763
[Bug 1130763] Pacemaker OCF volume Resource Agent fails when bricks are in
different domain to the system hostname.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=28jX0IC66P&a=cc_unsubscribe
More information about the Bugs
mailing list