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.
DescriptionAbhijeet Sadawarte
2016-01-28 14:13:42 UTC
Created attachment 1119173[details]
kickstart configuration file
Description of problem:
Launched kickstart installation with partitioning scheme containing encrypted LVs (one of them for swap). All of the partitions/LVs are created as expected after installation, including encryption, however the swap LV isn't in use and there is no record for the swap LV in /etc/fstab.
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 7.2
How reproducible:
Install Red Hat Enterprise Linux 7.2, create a PV containing: 1. LV for /, 2. encrypted LV for /home, 3. encrypted LV for swap (see the attached kickstart file)
Steps to Reproduce:
1.Install Red Hat Enterprise Linux 7.2 (see the attached kickstart file), create a PV containing: a) /boot (primary), b) LVM PV containing b1) LV for /, b2) encrypted LV for /home, b3) encrypted LV for swap (with the same passphrase for both LVs)
2. After reboot, check whether swap is in use (swapon -s)
3. Check the content of /etc/fstab
Actual results:
There is no record for the swap LV in /etc/fstab, nor is the swap LV active.
Expected results:
The swap LV should have been in use (should be listed in /proc/swaps or after running swapon -s) and there should have been a line describing the swap LV in /etc/fstab.
Additional info:
The same behavior could be seen as well with plain partitions (without LVM) - just comment out the logvol* and volgroup lines in favor of the part* lines in the kickstart config file.
Hello,
I did a test install using Server ISO and according to kickstart, I have not found any issue that would lead to unused swap partition on encrypted LVM.
I would like to ask you for additional installation logs.
I used the kickstart you provided and on my test machine, the swap entry is in /etc/fstab as well as swapon -s returns:
Filename Type Size Used Priority
/dev/dm-3 partition 522236 0 -1
Comment 4Abhijeet Sadawarte
2016-03-03 07:07:10 UTC
Hello Karel,
I did a test install again in my kvm setup and this time I've made one change in my kickstart file is, I have added '--passphrase=<password>' option as given below:
~~~
bootloader --append="rhgb quiet crashkernel=auto" --location=mbr --driveorder="sda" --boot-drive=sda
zerombr
clearpart --all --initlabel
part /boot --fstype="ext4" --ondisk=sda --size=512
part pv.95 --fstype="lvmpv" --ondisk=sda --size=19967
volgroup VolGroup00 --pesize=4096 pv.95
logvol / --fstype="ext4" --grow --size=10240 --encrypted --name=lv_root --vgname=VolGroup00 --passphrase=<redhat@123>
logvol swap --fstype="swap" --size=512 --encrypted --name=lv_swap --vgname=VolGroup00 --passphrase=<redhat@123>
~~~
And I came across same issue. Please check below outputs from my test vm:
~~~
https://paste.fedoraproject.org/332680/
~~~
JFYI when I tested the same kickstart without '--passphrase' option then during the installation anaconda prompted for encryption passphrase and I got expected result.
I am attaching anaconda logs when I faced this issue with '--passphrase' option in kickstart 'logvol' line.
Let me know if you need anything from my end.
- Regards,
Abhijeet Sadawarte
GSS, Red Hat
Comment 5Abhijeet Sadawarte
2016-03-03 07:12:43 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, 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://rhn.redhat.com/errata/RHEA-2016-2158.html
Created attachment 1119173 [details] kickstart configuration file Description of problem: Launched kickstart installation with partitioning scheme containing encrypted LVs (one of them for swap). All of the partitions/LVs are created as expected after installation, including encryption, however the swap LV isn't in use and there is no record for the swap LV in /etc/fstab. Version-Release number of selected component (if applicable): Red Hat Enterprise Linux 7.2 How reproducible: Install Red Hat Enterprise Linux 7.2, create a PV containing: 1. LV for /, 2. encrypted LV for /home, 3. encrypted LV for swap (see the attached kickstart file) Steps to Reproduce: 1.Install Red Hat Enterprise Linux 7.2 (see the attached kickstart file), create a PV containing: a) /boot (primary), b) LVM PV containing b1) LV for /, b2) encrypted LV for /home, b3) encrypted LV for swap (with the same passphrase for both LVs) 2. After reboot, check whether swap is in use (swapon -s) 3. Check the content of /etc/fstab Actual results: There is no record for the swap LV in /etc/fstab, nor is the swap LV active. Expected results: The swap LV should have been in use (should be listed in /proc/swaps or after running swapon -s) and there should have been a line describing the swap LV in /etc/fstab. Additional info: The same behavior could be seen as well with plain partitions (without LVM) - just comment out the logvol* and volgroup lines in favor of the part* lines in the kickstart config file.