Bug 1030659

Summary: GlusterFS volume/snapshot operations require locking
Product: Red Hat OpenStack Reporter: Eric Harney <eharney>
Component: openstack-cinderAssignee: Eric Harney <eharney>
Status: CLOSED DUPLICATE QA Contact: Haim <hateya>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.0CC: eharney, hateya, yeylon
Target Milestone: beta   
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-22 15:23:34 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:
Bug Depends On:    
Bug Blocks: 1021966    

Description Eric Harney 2013-11-14 21:23:29 UTC 
Description of problem:
GlusterFS volume/snapshot create/delete/extend operations need to use locking to prevent multiple threads from modifying on-disk data at the same time.

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

How reproducible:
Easily with the tweaks below, not often in general.

Steps to Reproduce:
To demonstrate this, add a time.sleep(15) call inside of _create_snapshot() immediately after the call self._create_qcow2_snap_file() and run many snapshot-create operations at once, then attempt to delete all of the snapshots that have been created.

Actual results:
Some of the snapshot delete operations fail.

Expected results:
All snapshot delete operations succeed.
Comment 1 Eric Harney 2013-11-22 15:23:34 UTC 

*** This bug has been marked as a duplicate of bug 1021966 ***