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.

Description of problem:
Right now, if an installclass which matches some product is used, autopartitioning can correctly set all values for the system.

However, if users select "Manual Partitioning", the values from the installclass (btrfs v LVM thin provisioning v regular LVM; xfs v ext4 v ...) are not used as defaults.

Instead, this values appear to be set by a constant, which is not customizable.

Expected results:

It should be possible to set some value in an installclass which changes these defaults if 'manual partitioning' is selected.

Could you please attach a file with the custom installclass and provide some concrete examples of the expected versus actual behaviour, please?

https://github.com/rhinstaller/anaconda/blob/rhel7-branch/pyanaconda/installclasses/rhv.py

You can see what we use "thin=true"

However, if you boot Anaconda in interactive mode and manual partitioning is selected, anaconda still defaults to regular, non-thin volumes.

+1 for this feature

Fix in a pull request: https://github.com/rhinstaller/anaconda/pull/941

Verified on RHEL-7.4-20170525.7 with anaconda-21.48.22.115-1.el7.

Thanks.

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://access.redhat.com/errata/RHBA-2017:2293