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.
This bug was initially created as a copy of Bug #1747468
I am copying this bug because: it applies to RHEL7 as well
Description of problem:
The code in PR https://github.com/rear/rear/pull/1806 (BZ #1450667) added support for restoring Thin volumes into ReaR 2.4.
Unfortunately it appears it doesn't work as planned.
1. When restoring the exact same system (which already had the VG containing the thin volumes configured at the time of the restore), the code used to delete the Thin pool after using vgcfgrestore is failing due to line 111 not returning an error, making line 112 return an error now
usr/share/rear/layout/prepare/GNU/Linux/110_include_lvm_code.sh:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
105 lvm lvs --noheadings -o lv_name,vg_name,lv_layout | while read lv vg layout ; do
106 # Consider LVs for our VG only
107 [ \$vg == "$vg" ] || continue
108 # Consider Thin Pools only
109 [[ ,\$layout, == *,thin,* ]] && [[ ,\$layout, == *,pool,* ]] || continue
110 # Remove twice, the first time it fails because of thin volumes in the pool
111 lvm lvremove -q -f -y \$vg/\$lv || true <-- HERE
112 lvm lvremove -q -f -y \$vg/\$lv
113 done
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
At the time PR1806 it was not the case, so there must have been some changed in LVM ...
2. When restoring a new system with same disk capacity (hence with clean new disk, this can be emulated by using "pvremove --force --force /dev/sdaX"), "vgcfgrestore" run but then "lvm lvremove" (line 111) fails with an unrecoverable error
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
+++ lvm lvremove -q -f -y rhel/pool00
Thin pool rhel-pool00-tpool (253:2) transaction_id is 10, while expected 6.
Failed to update pool rhel/pool00.
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Version-Release number of selected component (if applicable):
rear-2.4 including Upstream ReaR
How reproducible:
Always
Steps to Reproduce:
1. Install a system with LVM Thin Provisioning and multiple volumes, keep the swap as a standard LVM volume
/: thin
/var: thin
/home: thin
/tmp: thin
swap: linear
2. Create a rescue ISO
3. Recover the system
Actual results:
See above
Expected results:
Additional info:
It looks like to me "vgcfgrestore" cannot be used at all as soon as there is a Thin volume.
I'm pretty sure it was working at the time PR1806 was submitted (June 2018), I need to test this again.
For the demo, I've added a linear swap device because additionally, in scenario 2 ("When restoring a new system"), the swap volume gets restored by vgcfgrestore but doesn't get activated, causing an error when formatting the swap (/dev/vg/swap is not present ...), this is yet an additional issue...
Red Hat Enterprise Linux 7 shipped it's final minor release on September 29th, 2020. 7.9 was the last minor releases scheduled for RHEL 7.
From intial triage it does not appear the remaining Bugzillas meet the inclusion criteria for Maintenance Phase 2 and will now be closed.
From the RHEL life cycle page:
https://access.redhat.com/support/policy/updates/errata#Maintenance_Support_2_Phase
"During Maintenance Support 2 Phase for Red Hat Enterprise Linux version 7,Red Hat defined Critical and Important impact Security Advisories (RHSAs) and selected (at Red Hat discretion) Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available."
If this BZ was closed in error and meets the above criteria please re-open it flag for 7.9.z, provide suitable business and technical justifications, and follow the process for Accelerated Fixes:
https://source.redhat.com/groups/public/pnt-cxno/pnt_customer_experience_and_operations_wiki/support_delivery_accelerated_fix_release_handbook
Feature Requests can re-opened and moved to RHEL 8 if the desired functionality is not already present in the product.
Please reach out to the applicable Product Experience Engineer[0] if you have any questions or concerns.
[0] https://bugzilla.redhat.com/page.cgi?id=agile_component_mapping.html&product=Red+Hat+Enterprise+Linux+7