Bug 1215545

Summary: NFS-Ganesha: Errors in pcs status when features.ganesha enable is run after a failover.
Product: [Community] GlusterFS Reporter: Meghana <mmadhusu>
Component: common-haAssignee: Kaleb KEITHLEY <kkeithle>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: mainlineCC: mzywusko, ndevos, sankarshan, skoduri
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-06 17:49:02 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 Meghana 2015-04-27 05:30:35 UTC
Description of problem:
pcs status shows errors after set up is run after a failover. 

Version-Release number of selected component (if applicable):



How reproducible:
Always


Steps to Reproduce:
1. execute gluster features.ganesha enable
2. kill ganesha on any of the nodes
3. execute gluster features.ganesha disable
4. execute gluster features.ganesha enable

Actual results:

Failed actions:
    nfs-mon_monitor_10000 on nfs1 'unknown error' (1): call=62, status=Timed Out, last-rc-change='Mon Apr 27 00:08:50 2015', queued=0ms, exec=10002ms
    nfs-mon_monitor_10000 on nfs4 'unknown error' (1): call=20, status=Timed Out, last-rc-change='Mon Apr 27 00:08:51 2015', queued=1ms, exec=10001ms



Expected results:
Shouldn't see error messages


Additional info: