Description of problem: Additional logging of LVM commands in VDSM code is being requested. Version-Release number of selected component (if applicable): RHV 4.1 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Merged upstream, for the 4.1 backport see bug 1451226.
(In reply to Gordon Watson from comment #0) > Description of problem: > > Additional logging of LVM commands in VDSM code is being requested. > > > Version-Release number of selected component (if applicable): > > RHV 4.1 > > > How reproducible: > > PLEASE PROVIDE the steps to reproduce to test this? > Steps to Reproduce: > 1. > 2. > 3. > > Actual results: > > > Expected results: > > > Additional info:
To reproduce, do these flows (using iSCSI or FC storage domain): - crate domain - create vm - run vm - stop vm - delete vm - delete domain With 4.1.2 and 4.1.3. You will see that there are almost no logs for lvm before the patch. To see only lvm logs, grep for '[storage.LVM]'.
Verified with the following code: --------------------------------------- ovirt-engine-4.2.0-0.0.master.20170523140304.git04be891.el7.centos.noarch vdsm-4.20.0-886.gitf9accf8.el7.centos.x86_64 Verified with the following scenario: --------------------------------------- - crate domain - create vm - run vm - stop vm - delete vm - delete domain There are now plentiful logs for storage.LVM Moving to VERIFIED!
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:1489
BZ<2>Jira Resync