Bug 1216039

Summary:	nfs-ganesha: Discrepancies with lock states recovery during migration
Product:	[Community] GlusterFS	Reporter:	Soumya Koduri <skoduri>
Component:	common-ha	Assignee:	Kaleb KEITHLEY <kkeithle>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	3.7.0	CC:	jthottan, kkeithle, mmadhusu, ndevos, skoduri
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1219485 (view as bug list)		Environment:
Last Closed:	2015-06-05 14:36:09 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:
Bug Depends On:
Bug Blocks:	1219485, 1227028, 1227206

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 ***