Bug #5170

fs_lvm does not lock lvm changes

Added by Javi Fontan over 3 years ago. Updated over 3 years ago.

Status:ClosedStart date:05/24/2017
Priority:NormalDue date:
Assignee:Javi Fontan% Done:

0%

Category:Drivers - Storage
Target version:Release 5.4
Resolution:fixed Pull request:
Affected Versions:OpenNebula 5.2

Description

Multiple lvm actions can be performed at the same time in different hosts, this can be fixed with a lock in the frontend node or adding support for BRIDGE_LIST.

Associated revisions

Revision 8ea71b1a
Added by Javi Fontan over 3 years ago

B #5170: add a lock to lvm actions in fs_lvm

Revision a8cd7ca0
Added by Javi Fontan over 3 years ago

Revert "B #5170: add a lock to lvm actions in fs_lvm"

This reverts commit 8ea71b1a46d63a5e0c9c71e77aee99cba37f0dd3.

flock can not be used with bash functions. Create a new
exec_and_lock function with lock.

Revision fa1ed2be
Added by Javi Fontan over 3 years ago

B #5170: add a lock to lvm actions in fs_lvm

Revision e15cdcce
Added by Vlastimil Holer over 3 years ago

B #5170: Common scripts function "exclusive", use in fs_lvm

Revision a414e4d5
Added by Javi Fontan over 3 years ago

Merge pull request #347 from vholer/bug-5170

B #5170: LVM exclusive locking

History

#1 Updated by Javi Fontan over 3 years ago

  • Assignee set to Vlastimil Holer

#2 Updated by Ruben S. Montero over 3 years ago

  • Assignee changed from Vlastimil Holer to Javi Fontan

#3 Updated by Vlastimil Holer over 3 years ago

  • Status changed from Pending to Closed
  • Resolution set to fixed

Also available in: Atom PDF