Bug 1470931

Summary: [RFE] Provide a way to safely run LVM commands
Product: Red Hat Enterprise Virtualization Manager Reporter: Germano Veit Michel <gveitmic>
Component: vdsmAssignee: Tal Nisan <tnisan>
Status: CLOSED DEFERRED QA Contact: Avihai <aefrat>
Severity: high Docs Contact:
Priority: medium    
Version: 4.1.3CC: ebenahar, gwatson, lsurette, mwest, nashok, pzhukov, srevivo, tnisan, ycui
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-01 14:48:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Germano Veit Michel 2017-07-14 03:49:16 UTC
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.

Comment 5 Sandro Bonazzola 2019-01-28 09:44:13 UTC
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.

Comment 8 Michal Skrivanek 2020-03-18 15:49:36 UTC
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

Comment 9 Michal Skrivanek 2020-03-18 15:52:19 UTC
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

Comment 10 Michal Skrivanek 2020-04-01 14:48:31 UTC
ok, closing. Please reopen if still relevant/you want to work on it.

Comment 11 Michal Skrivanek 2020-04-01 14:51:39 UTC
ok, closing. Please reopen if still relevant/you want to work on it.