Public bug reported:
Recently I was running tempest for Manila,
I noticed some times, Test cases issued 2 delete snapshot command nearly in the
same time and
these 2 api call came to our backend driver in a row within 0.6 s, below the
manila api/driver call sequence in time line:
18:20:56.264 DELETE_1 cames via HTTP DELETE
18:20:56.86 DELETE_2 cames vai HTTP POST(Action body:
{"os-force_delete": null})
18:20:57.414 DELETE_1 finisned in driver
18:20:57.474 DELETE_2 finisned in driver
that's say, driver will received 2nd delete_snapshot request while processing
the 1st delete_snapshot.
while from Cinder, cinder manager will not dispatch the 2nd delete_snapshot
request to driver until 1nd delete_snapshot finished ,since cinder add
@locked_snapshot_operation for delete_snapshot
my question is : can Manila also add lock as cinder do?
Thanks
Peter
** Affects: manila
Importance: Undecided
Status: New
** Package changed: manila (Ubuntu) => manila
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479174
Title:
Lock required in delete share/snapshot
To manage notifications about this bug go to:
https://bugs.launchpad.net/manila/+bug/1479174/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
