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:
We currently completely ignore existing LVM VDO pools and LVs in blivet. We should be able to recognize these LVs and safely remove them in the Custom spoke in Anaconda and clearpart.
How reproducible:
Existing VG with a VDO pool:
# lvs vdo
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
vdo0 vdo vwi-a-v--- 25.00g vdopool 0.00
vdopool vdo dwi------- 5.00g 60.08
Same VG as seen by blivet (without children/LVs):
LVMVolumeGroupDevice instance (0x7fdafe341438) --
name = vdo status = True id = 86
children = []
parents = ['existing 10 GiB partition vdb1 (77) with existing lvmpv']
uuid = 32L5Rr-3Spu-T0OF-7609-94Hp-JVFT-TzFdml size = 10 GiB
format = existing None
major = 0 minor = 0 exists = True protected = False
sysfs path =
target size = 10 GiB path = /dev/vdo
format args = [] original_format = None free = 5 GiB PE Size = 4 MiB PE Count = 2559
PE Free = 1279 PV Count = 1
modified = False extents = 2559 free space = 10 GiB
free extents = 2559 reserved percent = 0 reserved space = 0 B
PVs = ['existing 10 GiB partition vdb1 (77) with existing lvmpv']
LVs = []
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 (python-blivet 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-2021:1890