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 1759972 - Cannot rename LVM LVs hosting encrypted Luks1 filesystems
Summary: Cannot rename LVM LVs hosting encrypted Luks1 filesystems
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: python-blivet
Version: 8.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: 8.0
Assignee: Vojtech Trefny
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-09 14:24 UTC by Renaud Métrich
Modified: 2021-09-06 15:33 UTC (History)
6 users (show)

Fixed In Version: python-blivet-3.2.2-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 03:22:23 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Screenshot showing name "varlogaudit" under mount point /var/log/audit but in reality "03" is the LV name (85.61 KB, image/png)
2019-10-09 14:24 UTC, Renaud Métrich 		no flags Details
View All

Description Renaud Métrich 2019-10-09 14:24:51 UTC 
Created attachment 1623830 [details]
Screenshot showing name "varlogaudit" under mount point /var/log/audit but in reality "03" is the LV name

Description of problem:

When installing a system using the GUI and choosing "Custom" for Storage Configuration and "Encryption", the MANUAL PARTITIONING panel opens.
Then there are 2 possibilities:

1. Clicking on "Click here to create them automatically"
or
2. Press the "+" button to start creating partitions

When using option 2. and adding partitions, the following happens:
- /boot is hosted on /dev/vda1 (OK)
- / is hosted on luks-rhel-00 logical volume
- /usr is hosted on luks-rhel-01 logical volume
- ...

It appears that all this ends up with having 1 VG created on /dev/vda2 and one LUKS1 device per logical volume.
There are then multiple issues appearing:
- Logical Volume name cannot be renamed through "Name:" field (e.g. from "00" to "root"): the description under the mount point left is updated, but not the "Name:" field
- LUKS2 cannot be chosen, the installer forces using LUKS1
- If the user wants a single LUKS2 volume similar to what is being created when clicking on "Click here to create them automatically", he needs to restart the partitioning from zero


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

RHEL8.0, 8.1 beta and RHEL7 Anaconda


How reproducible:

Always, see above description.
Comment 1 Ondrej Kozina 2019-11-13 11:51:18 UTC 
(In reply to Renaud Métrich from comment #0)
> - LUKS2 cannot be chosen, the installer forces using LUKS1

This is bad with regard to LUKS2 being default format in RHEL8. Can we get this fixed in 8.2?
Comment 2 Vendula Poncova 2020-04-15 13:15:53 UTC 
This bug contains multiple issues, so for ease of tracking and fixing them, we're going to split things up. The root issue of this bug should be fixed in blivet. The issue of allowing users to choose a LUKS version will be tracked in 1784360. Default creation of a vg with LUKS2 is fixed upstream and will be pulled in via a planned rebase for 8.3.
Comment 3 David Lehman 2020-04-21 20:43:36 UTC 
To encrypt the PV/VG rather than individual LVs, click on "Modify" below "Volume Group" and you can enable the encryption checkbox in the dialog that appears.
Comment 4 Vojtech Trefny 2020-05-14 11:40:29 UTC 
upstream PR: https://github.com/storaged-project/blivet/pull/836
Comment 10 errata-xmlrpc 2020-11-04 03:22:23 UTC 
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-2020:4728
Note You need to log in before you can comment on or make changes to this bug.