This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
I'm convinced it could be matched with Bug #1108540 since dmeventd is directly involved. It's fixed with release of 2.02.112
We need to inspect more here - I don't think this is exactly the same as bug #1108540 - the errors differ. While in bug #1108540 we always had "dm_task_run failed, errno = 6, No such device or address", here we have "dm_task_run failed, errno = 22, Invalid argument" which seems to be a different issue (wrong table supplied while dmeventd is trying to fixup LVs).
New dmeventd code in version 2.02.133 should resolve most of spurious dm_task_run errors flowing out of dmeventd process.
My view here is - once we release this version - and we get another fail case with dm_task_run - take it as a new bug.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see email@example.com with any questions
I have not seen any of these messages in quite some time on any of the nodes doing raid regression testing. Marking verified.
lvm2-2.02.161-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016
lvm2-libs-2.02.161-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016
lvm2-cluster-2.02.161-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016
device-mapper-1.02.131-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016
device-mapper-libs-1.02.131-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016
device-mapper-event-1.02.131-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016
device-mapper-event-libs-1.02.131-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016
device-mapper-persistent-data-0.6.3-1.el7 BUILT: Fri Jul 22 05:29:13 CDT 2016
cmirror-2.02.161-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016
sanlock-3.4.0-1.el7 BUILT: Fri Jun 10 11:41:03 CDT 2016
sanlock-lib-3.4.0-1.el7 BUILT: Fri Jun 10 11:41:03 CDT 2016
lvm2-lockd-2.02.161-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016
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.