Bug 1516650

Summary: [GSS](6.4.z) Failback not working on NFSv4
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Tom Ross <tom.ross>
Component: JMSAssignee: Tom Ross <tom.ross>
Status: CLOSED CURRENTRELEASE QA Contact: Peter Mackay <pmackay>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.18CC: bmaxwell, dosoudil, jbilek, jmesnil
Target Milestone: CR1   
Target Release: EAP 6.4.19   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1519198 (view as bug list) Environment:
Last Closed: 2018-04-16 11:03:37 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: 1498153, 1498190, 1519198    

Description Tom Ross 2017-11-23 08:09:01 UTC 
If Artemis is using NFSv4 as shared store for its messaging journal to provide HA then a write to server.lock made by one server may not be propagated to the other server. This prevents failback from happening. This is change in behavior in data synchronization between two NFSv4 clients was observed when recently upgrading Linux platforms.
Comment 4 Jiří Bílek 2018-01-17 12:22:13 UTC 
Verified with EAP 6.4.19.CP.CR2