Bug 1215545 - NFS-Ganesha: Errors in pcs status when features.ganesha enable is run after a failover.
Summary: NFS-Ganesha: Errors in pcs status when features.ganesha enable is run after a...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: common-ha
Version: mainline
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Kaleb KEITHLEY
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-27 05:30 UTC by Meghana
Modified: 2017-03-06 17:49 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-03-06 17:49:02 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

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:
Note You need to log in before you can comment on or make changes to this bug.