Bug 1759972
| Summary: | Cannot rename LVM LVs hosting encrypted Luks1 filesystems | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Renaud Métrich <rmetrich> | ||||
| Component: | python-blivet | Assignee: | Vojtech Trefny <vtrefny> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 8.0 | CC: | jstodola, kwalker, okozina, pzatko, vponcova, vtrefny | ||||
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
||||
| Target Release: | 8.0 | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | python-blivet-3.2.2-1.el8 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-11-04 03:22:23 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
(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? 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. 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. upstream PR: https://github.com/storaged-project/blivet/pull/836 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 |
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.