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:
For RHVH we are using a custom installclass to set the autopartitioning, this works fine.

But as soon as the user chooses manul partitioning, he is completely free in doing the partitioning. The issue is that RHVH has a few (4?) constraints like
- Needs to be thin LV for /
- /boot must be >=1GB
- /var must be on a separate LV or partition
- /var must be at least 10GB

We would like to have a way to express these constraints from the installclass.

Version-Release number of selected component (if applicable):
7.3

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

A pull request with a fix is available here: https://github.com/rhinstaller/anaconda/pull/972

One of the commits adds required constraints to the class OvirtBaseInstallClass. Is it all right or do you use your own install class?

That's the installclass we use, and the changes look good, so +1 from me.

The patch is present in anaconda anaconda-21.48.22.115-1.el7. Moving to VERIFIED (SanityOnly).

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