PowerMax driver - solve issue of concurrent snapvx operations

Bug #1812231 reported by Helen Walsh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Undecided
Helen Walsh

Bug Description

Stricter locking is required around snapvx operations to prevent concurrency issues, most notibly around the 'create_volume_from_volume' api and the use of snapvx generations.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

Fix proposed to branch: master
Review: https://review.openstack.org/631534

Changed in cinder:
assignee: nobody → Helen Walsh (walshh2)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

Reviewed: https://review.openstack.org/631534
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=1e6eb4c0e91a4fa1e91055e3044cc84ff9fe4520
Submitter: Zuul
Branch: master

commit 1e6eb4c0e91a4fa1e91055e3044cc84ff9fe4520
Author: Helen Walsh <email address hidden>
Date: Thu Jan 17 15:30:44 2019 +0000

    PowerMax driver - solve issue of concurrent snapvx operations

    Stricter locking is required around snapvx operations on the same source
    volume to prevent concurrency issues, most notibly around the
    'create_cloned_volume' api and the use of snapvx generations.

    Change-Id: Ia509adedfa937b7770de8a9a603d4aac0dce71e7
    Closes-Bug: #1812231

Changed in cinder:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/cinder 14.0.0.0rc1

This issue was fixed in the openstack/cinder 14.0.0.0rc1 release candidate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.