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.

Description of problem:
-----------------------
This issue is seen with RHHI-V deployment, in which RHVH node is used. When the node has a thinpool device and LVM cache attached to the thinpool

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
python3-blivet-3.1.0-20.el8.noarch
blivet-data-3.1.0-20.el8.noarch
kernel-4.18.0-193.el8.x86_64

How reproducible:
------------------
Always

Steps to Reproduce:
--------------------
1. Create a LVM thinpool with a disk
2. Attach the LVM cache to this thinpool
3. Use blivet to enquire about the devices

Actual results:
---------------
Tracebacks seen in /var/log/messages 

Expected results:
-----------------
No tracebacks should be seen

Created attachment 1686131 [details]
error snip in /var/log/messages

Created attachment 1686146 [details]
sosreport from the node

Created attachment 1686148 [details]
/var/log/messages from the node

upstream PR: https://github.com/storaged-project/libblockdev/pull/524

This bug is now proposed for RHEL 8.3.

Though there are no associated functionality loss, there are lots of traceback in /var/log/messages which may upset the customer
and also increases the storage space consumption of /var/log. With these reasoning, I am proposing this bug to be fixed in 
for RHEL 8.2.z

@Vojtech, do you agree with me ?
Is it possible to have the fix available in RHEL 8.2.z ?

I think we can fix this in 8.2.z. I've cloned this bug for 8.2 -- https://bugzilla.redhat.com/show_bug.cgi?id=1836189 I hope I've set all the flags and release targets correctly.

Hello

test pass  libblockdev-2.24-1.el8 tests function LvmPVVGcachedThpoolstatsTestCase, so move 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 (libblockdev bug fix and enhancement update), 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-2020:4734