Caching images doesn't like concurrency

Bug #1670716 reported by Andriy Kurilin
This bug report is a duplicate of:  Bug #1649636: Duplicate volumes in image cache. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
New
Undecided
Unassigned

Bug Description

In case of N concurrent requests for volumes creation from one image, Cinder API creates N cache images.

While debugging resource leak in rally-cinder job, we discovered that we have a lot of cache volumes with equal names (image-<uuid>).

Simple rally scenario for reproduce:
http://logs.openstack.org/60/442460/2/check/gate-rally-dsvm-rally-cinder-nv/982b4b6/rally-plot/results.html.gz#/CinderVolumes.create_and_get_volume/overview

Logs:
* unexpected resources (not created by rally directly)
http://logs.openstack.org/60/442460/2/check/gate-rally-dsvm-rally-cinder-nv/982b4b6/rally-plot/resources_diff.txt.gz

* job logs
http://logs.openstack.org/60/442460/2/check/gate-rally-dsvm-rally-cinder-nv/982b4b6/logs/

description: updated
Revision history for this message
Eric Harney (eharney) wrote :

This is being addressed in bug 1649636.

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.