OpenStack Shared File Systems Service (Manila)

service_instance module does not have locks for shared resources

Bug #1321340 reported by Valeriy Ponomaryov on 2014-05-20

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	OpenStack Shared File Systems Service (Manila)	Fix Released	High	Unassigned

Bug Description

service_instance module operates not only with individual VMs, but with shared resources too. So all methods, that create/modify shared resources (service network, subnets, ports...) should have locks.

See original description

Valeriy Ponomaryov (vponomaryov) on 2014-05-20

Changed in manila:
importance:	Undecided → High

Valeriy Ponomaryov (vponomaryov) on 2014-05-20

description:

updated

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2014-05-23: Fix merged to manila (master)

Reviewed: https://review.openstack.org/94655
Committed: https://git.openstack.org/cgit/stackforge/manila/commit/?id=49ecd33651c15c3bded1da7e4af2b23e85675e35
Submitter: Jenkins
Branch: master

commit 49ecd33651c15c3bded1da7e4af2b23e85675e35
Author: Valeriy Ponomaryov <email address hidden>
Date: Wed May 21 11:51:50 2014 -0400

Added locks into service_instance module

service_instance module should have interprocess
locks due to work with shared resources for whole manila service

Change-Id: I199098271c095b04f887928fec7c7620a8af03a4
Closes-Bug: #1321340

Changed in manila:
status:	New → Fix Committed

Valeriy Ponomaryov (vponomaryov) on 2014-05-23

Changed in manila:
status:	Fix Committed → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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