Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1601016

Summary: Need to make sure VDO dmeventd plugin is part of LVM2 package for 7.6
Product: Red Hat Enterprise Linux 7 Reporter: bjohnsto
Component: lvm2Assignee: Zdenek Kabelac <zkabelac>
lvm2 sub component: dmeventd QA Contact: cluster-qe <cluster-qe>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: unspecified CC: agk, cmarthal, heinzm, jbrassow, msnitzer, prajnoha, rhandlin, thornber, zkabelac
Version: 7.6   
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: lvm2-2.02.180-2.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1601018 (view as bug list) Environment:
Last Closed: 2018-10-30 11:03:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1519307, 1601018, 1654309    

Description bjohnsto 2018-07-13 15:12:50 UTC 
Description of problem:

VDO and LVM have come up with a plugin for dmeventd that monitors VDO volumes. We want to make sure that plugin makes it into the LVM2 package for 7.6


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 Corey Marthaler 2018-07-30 15:37:08 UTC 
Is this what's responsible for all the following errors in the logs now?

Jul 30 10:17:38 hayes-02 UDS/vdodmeventd[144687]: ERROR  (vdodmeventd/144687) The dynamic shared library libdevmapper-event-lvm2vdo.so could not be loaded: libdevmapper-event-lvm2vdo.so: cannot open shared object file: No such file or directory
Jul 30 10:17:38 hayes-02 UDS/vdodmeventd[144687]: ERROR  (vdodmeventd/144687) Failed to load the dmeventd plugin
Comment 6 Zdenek Kabelac 2018-08-01 14:12:35 UTC 
Stable branch received these 2 patches:

https://www.redhat.com/archives/lvm-devel/2018-July/msg00086.html
https://www.redhat.com/archives/lvm-devel/2018-July/msg00087.html


The only thing this VDO dmeventd plugin is doing - it monitors UUID VDO device, and when the usage reaches 80%, 85%, 90%, 95%, 100%  WARNING is issued to syslog.

Since lvm2 in stable branch does not support VDO - there is no way to test this functionality with lvm2 itself.

Plugin should allow vdo tools to register their UUIDs.
Comment 8 Corey Marthaler 2018-08-27 21:19:53 UTC 
It appears to be a part of the latest rpm. Marking verified.

[root@hayes-01 ~]# rpm -ql lvm2-libs | grep vdo
/usr/lib64/device-mapper/libdevmapper-event-lvm2vdo.so
/usr/lib64/libdevmapper-event-lvm2vdo.so


3.10.0-937.el7.x86_64

lvm2-2.02.180-6.el7    BUILT: Fri Aug 24 08:52:19 CDT 2018
lvm2-libs-2.02.180-6.el7    BUILT: Fri Aug 24 08:52:19 CDT 2018
lvm2-cluster-2.02.180-6.el7    BUILT: Fri Aug 24 08:52:19 CDT 2018
lvm2-lockd-2.02.180-6.el7    BUILT: Fri Aug 24 08:52:19 CDT 2018
lvm2-python-boom-0.9-9.el7    BUILT: Fri Aug 24 08:52:54 CDT 2018
cmirror-2.02.180-6.el7    BUILT: Fri Aug 24 08:52:19 CDT 2018
device-mapper-1.02.149-6.el7    BUILT: Fri Aug 24 08:52:19 CDT 2018
device-mapper-libs-1.02.149-6.el7    BUILT: Fri Aug 24 08:52:19 CDT 2018
device-mapper-event-1.02.149-6.el7    BUILT: Fri Aug 24 08:52:19 CDT 2018
device-mapper-event-libs-1.02.149-6.el7    BUILT: Fri Aug 24 08:52:19 CDT 2018
device-mapper-persistent-data-0.7.3-3.el7    BUILT: Tue Nov 14 05:07:18 CST 2017
Comment 10 errata-xmlrpc 2018-10-30 11:03:51 UTC 
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/RHBA-2018:3193