Description of problem: We have recently learned that running lvm commands without proper parameters with lvmetad running can ruin a Storage Domain. We also know that to run LVM commands safely, the Storage Domain must be in maintenance mode in order to prevent them from clashing with SPM lvm commands. However, maintenance mode is hardly accepted by customers as it puts all the VMs of the Storage Domain down. This is undesirable, correcting a single failure (removing an orphan LV or changing a tag) should not require the entire Storage Domain to be shutdown, these are often production VMs. What is requested here is some sort of: vdsm-client run-lvm-command <my lvm command here> vdsm would then take care of running this command, adding the required configuration such as lvmetad=0 and also ensuring no other LVM command runs in parallel and also the current host is still the SPM at the time the command is issued.
This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly
ok, closing. Please reopen if still relevant/you want to work on it.