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.

Description of problem:
I'm still trying to figure out what state or cmd exactly causes these. It appears many of the lvm cmds can result in these types messages.

[root@hayes-02 ~]# grep "Failed to parse status."  /var/log/messages | wc -l
182558


Version-Release number of selected component (if applicable):
kernel-4.18.0-48.el8    BUILT: Sat Dec  1 19:25:48 CST 2018
lvm2-2.03.01-1.el8    BUILT: Thu Nov  1 04:29:08 CDT 2018
lvm2-libs-2.03.01-1.el8    BUILT: Thu Nov  1 04:29:08 CDT 2018
lvm2-dbusd-2.03.01-1.el8    BUILT: Thu Nov  1 04:31:09 CDT 2018
lvm2-lockd-2.03.01-1.el8    BUILT: Thu Nov  1 04:29:08 CDT 2018
boom-boot-0.9-5.el8    BUILT: Wed Sep 19 16:56:59 CDT 2018
cmirror-2.03.01-1.el8    BUILT: Thu Nov  1 04:29:08 CDT 2018
device-mapper-1.02.153-1.el8    BUILT: Thu Nov  1 04:29:08 CDT 2018
device-mapper-libs-1.02.153-1.el8    BUILT: Thu Nov  1 04:29:08 CDT 2018
device-mapper-event-1.02.153-1.el8    BUILT: Thu Nov  1 04:29:08 CDT 2018
device-mapper-event-libs-1.02.153-1.el8    BUILT: Thu Nov  1 04:29:08 CDT 2018
device-mapper-persistent-data-0.7.6-1.el8    BUILT: Sun Aug 12 04:21:55 CDT 2018

Surely failure in parsing is bug and should not happen - so there is some status line of some dm target where lvm2 is not able to properly parse it - I can assume it's result of dmeventd monitoring.

So when you get the message logged - please attach also 'dmsetup table' & 'dmsetup status'.

I'd guess this could have been related with the change of dm cache status line fixed with this commit:

https://www.redhat.com/archives/lvm-devel/2019-June/msg00006.html

So closing - if there is still something like this - we would need to know exact cause.
As the reported message is important and needs fix in lvm2 code to enahance parser to understand new status information.

As the bug has been already fixed in several releases - closing as 'CURRENTRELEASE' with assumption such message are gone already for long time (fixed in 2019).