Bug #5170
fs_lvm does not lock lvm changes
| Status: | Closed | Start date: | 05/24/2017 | |
|---|---|---|---|---|
| Priority: | Normal | Due 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
B #5170: add a lock to lvm actions in fs_lvm
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.
B #5170: add a lock to lvm actions in fs_lvm
B #5170: Common scripts function "exclusive", use in fs_lvm
History
#1
Updated by Javi Fontan about 4 years ago
- Assignee set to Vlastimil Holer
#2
Updated by Ruben S. Montero almost 4 years ago
- Assignee changed from Vlastimil Holer to Javi Fontan
#3
Updated by Vlastimil Holer almost 4 years ago
- Status changed from Pending to Closed
- Resolution set to fixed