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.
Bug 1855972 - Cannot create LV with cache when PV is encrypted
Summary: Cannot create LV with cache when PV is encrypted
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.8
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-11 12:19 UTC by Renaud Métrich
Modified: 2023-10-06 21:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-11 21:51:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Kickstart for reproducing (can be used on RHEL7) (1.72 KB, text/plain)
2020-07-11 12:22 UTC, Renaud Métrich
no flags Details
Screenshot of error (17.86 KB, image/png)
2020-07-11 12:24 UTC, Renaud Métrich
no flags Details

Description Renaud Métrich 2020-07-11 12:19:37 UTC
Description of problem:

Trying to install a system with a cached LV and PVs Luks encrypted, the installer complains with the following message:

  Cache PVs must belong to the same VG as the cached LV

Kickstart excerpt:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
part pv.00 --ondisk=/dev/vda --size=1 --grow --encrypted --passphrase="redhat"
part pv.01 --ondisk=/dev/vdb --size=1 --grow --encrypted --passphrase="redhat"
volgroup rhel pv.00 pv.01
logvol swap --fstype="swap" --size=1024 --name=swap --vgname=rhel
logvol / --fstype="xfs" --size=8192 --name=root --vgname=rhel
logvol /data --fstype="xfs" --size=4096 --name=data --vgname=rhel --cachepvs=pv.01 --cachesize=8192 --cachemode=writeback 
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

In the example above, /data is hosted on rhel/data LV with cache PV pv.01 encrypted.
Even though pv.01 is building "rhel" volume group, the code doesn't detect that.

My hypothesis is that there is no code to handle the fact that "pv.01" is not the PV here, but the luks-encrypted device /dev/vdb.


Version-Release number of selected component (if applicable):

RHEL7 and RHEL8.2.0


How reproducible:

ALWAYS


Steps to Reproduce:
1. Install a system with a kickstart having 2 disks (see attachment for kickstart)

Actual results:

"Cache PVs must belong to the same VG as the cached LV"


Expected results:

Installs fine

Additional info:

The "workaround" I found is to use encrypted filesystems instead of encrypted PVs:

-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
part pv.00 --ondisk=/dev/vda --size=1 --grow
part pv.01 --ondisk=/dev/vdb --size=1 --grow
volgroup rhel pv.00 pv.01
logvol swap --fstype="swap" --size=1024 --name=swap --vgname=rhel --encrypted --passphrase="redhat"
logvol / --fstype="xfs" --size=8192 --name=root --vgname=rhel --encrypted --passphrase="redhat"
logvol /data --fstype="xfs" --size=4096 --name=data --vgname=rhel --cachepvs=pv.01 --cachesize=8192 --cachemode=writeback --encrypted --passphrase="redhat"
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

Comment 2 Renaud Métrich 2020-07-11 12:22:19 UTC
Created attachment 1700692 [details]
Kickstart for reproducing (can be used on RHEL7)

Comment 3 Renaud Métrich 2020-07-11 12:24:20 UTC
Created attachment 1700693 [details]
Screenshot of error

Comment 4 Vojtech Trefny 2020-07-13 13:03:05 UTC
Switching to anaconda, the problem is in the custom partitioning code, not in blivet (see proposed fix for 1855973).

Comment 8 Chris Williams 2020-11-11 21:51:24 UTC
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


Note You need to log in before you can comment on or make changes to this bug.