Bug 1030659 - GlusterFS volume/snapshot operations require locking
Summary: GlusterFS volume/snapshot operations require locking
Keywords:
Status: CLOSED DUPLICATE of bug 1021966
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 4.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: beta
: 4.0
Assignee: Eric Harney
QA Contact: Haim
URL:
Whiteboard: storage
Depends On:
Blocks: 1021966
TreeView+ depends on / blocked
 
Reported: 2013-11-14 21:23 UTC by Eric Harney
Modified: 2016-04-26 15:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-22 15:23:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1251425 0 None None None Never
OpenStack gerrit 56462 0 None MERGED GlusterFS: Synchronize operations that manipulate qcow2 data 2020-07-29 12:58:15 UTC

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


Note You need to log in before you can comment on or make changes to this bug.