Bug 1396194

Summary: Ganesha heartbeat through crm_attribute send warnings if nodes are configured with FQDN
Product: [Community] GlusterFS Reporter: Natale Vinto <nvinto>
Component: ganesha-nfsAssignee: Kaleb KEITHLEY <kkeithle>
Status: CLOSED EOL QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs, kkeithle, pasik
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-20 08:56:05 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:
Attachments:
Description Flags
ganesha-ha.conf none

Description Natale Vinto 2016-11-17 17:26:23 UTC 
Created attachment 1221611 [details]
ganesha-ha.conf

Description of problem:

Hello, using Red Hat Gluster Storage 3.1 based on GlusterFS 3.7.9 on RHEL 7 with Ganesha NFA HA, with a cluster with 3 nodes (2 + 1 dummy) and 1 replica 2 ganesha.enable on volume.
I got lots of warning from /var/log/messages from ganesha heartbeat. I configured nodes as shown in the documentation example [1][2]

Using FQDN for hostnames, such as node1.example.local, node2.example.local in /etc/ganesha/ganesha-ha.conf

Nov 17 10:18:09 node1 ganesha_mon(nfs-mon)[31542]: INFO: mon monitor warning: crm_attribute --node=node1 --name=grace-active --update=0 failed
Nov 17 10:18:24 node1 ganesha_mon(nfs-mon)[31780]: INFO: mon monitor warning: crm_attribute --node=node1 --name=grace-active --update=0 failed
Nov 17 10:18:39 node1 ganesha_mon(nfs-mon)[31999]: INFO: mon monitor warning: crm_attribute --node=node1 --name=grace-active --update=0 failed
Nov 17 10:18:54 node1 ganesha_mon(nfs-mon)[32207]: INFO: mon monitor warning: crm_attribute --node=node1 --name=grace-active --update=0 failed

# pcs cluster status
Cluster Status:
 Stack: corosync
 Current DC: node2.example.local (version 1.1.15-11.el7_3.2-e174ec8) - partition with quorum
 Last updated: Thu Nov 17 18:13:24 2016         Last change: Thu Nov 17 13:10:37 2016 by root via crm_attribute on node1.example.local
 2 nodes and 8 resources configured

PCSD Status:
  node1.example.local: Online
  node2.example.local: Online

Attached ganesha-ha.conf


looking at the code [1] it looks that the short name of the hostname is used to trigger heartbeat, so I was wondering if FQDN HA_CLUSTER_NODES are supported with ganesha heartbeat or if I miss something.

My /etc/resolv.conf contains:

domain example.local
search example.local
nameserver 10.0.1.2
nameserver 10.0.1.3



[1] https://gluster.readthedocs.io/en/latest/Administrator%20Guide/NFS-Ganesha%20GlusterFS%20Integration/
[2] https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html-single/Administration_Guide/index.html#sect-NFS_Ganesha
[3] https://github.com/gluster/glusterfs/blob/master/extras/ganesha/ocf/ganesha_mon#L190


Version-Release number of selected component (if applicable):
GlusterFS3.7.9
RHGS 3.1

How reproducible:


Steps to Reproduce:
1. Install ganesha nfs ha
2. Configure cluster nodes with FQDN and start a ganesha volume
3. check /var/log/messages for warnings

Actual results:
 ganesha_mon(nfs-mon)[31542]: INFO: mon monitor warning: crm_attribute --node=node1 --name=grace-active --update=0 failed


Expected results:

no warning


Additional info:
Comment 1 Jiffin 2018-11-20 08:56:05 UTC 
The ganesha HA solution is moved from pacemaker/corosync to stohaug which uses ctdb. Hence closing this bug as EOLed