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.

Document URL: 
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7-Beta/html/Installation_Guide/sect-kickstart-syntax.html#idp5437416
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-kickstart-syntax.html#idp6984552

Section Number and Name: 

Describe the issue: 
--percent says it cant be used with size or grow. --grow does not mention this limitation and the examples at the bottom of the section include --grow --size and --percent which is incorrect as per the documentation

Suggestions for improvement: 
under --grow state that it should not be used with --percent (I've tried this on a 7.1 install and whilst allowed the server grew the volume to fill the LV)
under the example useage have valid syntax, with 2 sections 1 with --grow and --size and another with --percent one just 1 section that is correct.

Additional information: 
having just tested a kickstart using 
logvol /  --fstype="xfs" --percent=75 --name=lv_root --vgname=vg_master
I can confirm that works correctly

Reassigning all of my bugs to the new DPM Tomas Capek.

Hello,

While investigating we found that the issue was somewhat different from what was reported. The actual behavior of --grow is that it will always attempt to fill all remaining space in the volume group (after all other volumes with statically defined sizes have been created), and it can be used with both --percent= and --size=. 

The actual behavior is:

1. The logical volume is created with a size set by either the --size= or --percent= parameter.
2. If the --grow option is present, the logical volume will then expand to fill all remaining space within the volume group, unless
3. The --maxsize= option is also used on the same volume, placing a limit on how much the volume can grow instead of filling all remaining space in the volume group.

A fix has been posted to the guide and descriptions for --size=, --percent=, --grow and --maxsize= should now be clearer.

Update published at https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-kickstart-syntax.html#sect-kickstart-commands

(scroll down or search for "logvol (optional)"