Created attachment 927478 [details]
Bugfix for glusterfs-resource-agents.noarch
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:
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):
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.
The volume does not start. The script always thinks the volume is already running.
The volume should start normally.
Bug 1147252 has been filed to get the change in the master branch. When that has been done it can get backported to release-3.5:
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.