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:
leapp preupgrade check failed as 'vdoprepareforlvm' unexpectedly throw an error on partitions with particularly small space.
Version-Release number of selected component (if applicable):
leapp version 0.14.0
How reproducible:
Always
Steps to Reproduce:
1. Create a partition with a small space (I have a bios boot partition https://en.wikipedia.org/wiki/BIOS_boot_partition that has 1MB space)
2. Run leapp preupgrade command
3. It Throws the following error
Actual results:
Risk Factor: high (inhibitor)
Title: VDO devices migration to LVM management
Summary: Unexpected result checking device
unexpected error from 'vdoprepareforlvm' for sda1; result = 2
Remediation: [hint] Resolve the conditions leading to the reported failure and re-run the upgrade.
Key: f7c335398cc449f5d7baf4e73255d44c34ad2620
Expected results:
preupgrade processes normal
Additional info:
Hi, thank you for the report. The problem is caused by vdoprepareforlvm utility. It's question whether the bug should be fixed in the vdo package or it's something what's expected to handle in the related leapp actor. See:
~~~
# /usr/libexec/vdoprepareforlvm --check /dev/vda1
vdoprepareforlvm: Unexpected error accessing '/dev/vda1' : VDO Status: Out of range
~~~
Joe, could you look at it?
In case that no VDO partitions are present on the system, the workaround for now is this:
# dnf remove -y vdo
# leapp answer --section check_vdo.no_vdo_devices=True
be aware, that if any vdo partition are present on the system, they will be lost after the upgrade if they are not migrated under lvm management prior the upgrade.
Hi, I will close this ticket as a duplicate of bug #2093220
as the root cause is same in both BZs despite different partitions.
The fix is to skip all partitions that are smaller than 4 MiB.
*** This bug has been marked as a duplicate of bug 2093220 ***