LVM access rules concurrency
Bug #1550378 reported by
Rodrigo Barbieri
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Medium
|
Valeriy Ponomaryov |
Bug Description
LVM drivers may have several backend configurations with different backend names in the same node. Currently the NFS code it uses employs a lock mechanism based on backend name. This way the lock does not conflict between the two backends, but both are modifying the same /etc/exports file when adding/removing access rules.
Changing to IP address still would not be a good enough fix because the same node may use one backend configuration per network interface. A new mechanism needs to be defined to lock the manila node affecting all backends registered.
tags: | added: bugsmash-mitaka |
Changed in manila: | |
assignee: | nobody → Valeriy Ponomaryov (vponomaryov) |
status: | New → In Progress |
To post a comment you must log in.
Is there a use case for 2 LVM backends on the same host, other than testing? Is the testing configuration important enough that this needs to be fixed?