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.

Bug 2220932

Summary: "Kickstart insufficient": LUKS doesn't work with lvm and --grow
Product: Red Hat Enterprise Linux 8 Reporter: Matt Castelein <matt.castelein>
Component: python-blivetAssignee: Blivet Maintenance Team <blivet-maint-list>
Status: CLOSED MIGRATED QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.3CC: jstodola
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-23 12:38:56 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:

Description Matt Castelein 2023-07-06 14:47:55 UTC
Description of problem:
Kickstart using LVM partitioning with LUKS does not accept the --grow option

How reproducible:
Always

Steps to Reproduce:
1. Kickstart using LUKS and LVM with a partition using --grow

Actual results:
"Kickstart insufficient" "('device cannot be smaller than 16 MiB', 'luks5'

Expected results:
Partition is created exactly as when not using LUKS

Additional info:
logvol /opt  --name=lv_opt --vgname=vg_rocsoft --size=1 --grow --fsoptions="nodev" --encrypted --cipher=aes-cbc-essiv:sha256 --passphrase=xxxxxx

Comment 1 Jan Stodola 2023-07-10 14:35:12 UTC
Matt, try using "... --size=32 --grow ...", it works for me.


The installer behavior is a bit confusing to me. With "--size=1 --grow" and enough free space in the VG - for example 1 GiB, I would expect the installer to create the partitioning with 1 GiB LV/LUKS device and not failing with 'device cannot be smaller than 16 MiB'. 
Reassigning to blivet and attach installation logs from an installation with the following partitioning:

bootloader --location=mbr
zerombr
clearpart --all --initlabel
part /boot --asprimary --size=500 --label=boot
part pv.01  --size=18000
volgroup SNAKEVG pv.01
logvol / --size=10000 --name=SNAKEROOT --vgname=SNAKEVG
logvol /opt --size=1 --grow --name=SNAKEOPT --vgname=SNAKEVG --encrypted --passphrase XYZ

Comment 3 Matt Castelein 2023-07-10 14:50:29 UTC
Confirmed the expected behavior with --size=32 --grow

Comment 4 Brian Lane 2023-07-10 23:10:42 UTC
This has been a quirk of '--size XX --grow' for years. The size needs to be larger than the minimum size of the partition is being created. So for / it needs to be big enough to hold the installed packages, and as the error says, in this case it has to be at least 16 MiB.

Comment 5 Matt Castelein 2023-07-11 12:41:15 UTC
(In reply to Brian Lane from comment #4)
> This has been a quirk of '--size XX --grow' for years. The size needs to be
> larger than the minimum size of the partition is being created. So for / it
> needs to be big enough to hold the installed packages, and as the error
> says, in this case it has to be at least 16 MiB.

Note that I only see the error when using --encrypted, otherwise it works fine with --size=1

Comment 6 RHEL Program Management 2023-09-23 12:36:08 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 7 RHEL Program Management 2023-09-23 12:38:56 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.