Bug 1216039 - nfs-ganesha: Discrepancies with lock states recovery during migration
Summary: nfs-ganesha: Discrepancies with lock states recovery during migration
Keywords:
Status: CLOSED DUPLICATE of bug 1227028
Alias: None
Product: GlusterFS
Classification: Community
Component: common-ha
Version: 3.7.0
Hardware: All
OS: All
high
high
Target Milestone: ---
Assignee: Kaleb KEITHLEY
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1219485 1227028 glusterfs-3.7.2
TreeView+ depends on / blocked
 
Reported: 2015-04-28 12:00 UTC by Soumya Koduri
Modified: 2015-12-01 16:45 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1219485 (view as bug list)
Environment:
Last Closed: 2015-06-05 14:36:09 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1224618 0 high CLOSED Ganesha server became unresponsive after successfull failover 2023-09-14 02:59:34 UTC

Internal Links: 1224618

Description Soumya Koduri 2015-04-28 12:00:38 UTC 
Description of problem:

We have seen below issue while testing open/lock states recovery after IP failover in nfs-ganesha HA setup - 

The cluster has not been put into grace before IP fails over. There seem to be a timing issue there. "pcs constraint colocation order" seem to have not completely solved it.
Comment 1 Kaleb KEITHLEY 2015-05-07 13:08:27 UTC 
yes, there's a race between setting grace and failing over the virt IP.

See http://review.gluster.org/10490
Comment 2 Niels de Vos 2015-06-02 08:20:16 UTC 
The required changes to fix this bug have not made it into glusterfs-3.7.1. This bug is now getting tracked for glusterfs-3.7.2.
Comment 3 Kaleb KEITHLEY 2015-06-05 14:36:09 UTC 
Not sure why I created 1227028 on release-3.7 branch. I may have meant for it to be downstream.

1219485 = main
1227028 = release-3.7
1224618 = downstream

*** This bug has been marked as a duplicate of bug 1227028 ***
Note You need to log in before you can comment on or make changes to this bug.