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.
Description of problem:
When a system has XFS file systems created with "ftype=0" attribute (e.g. system was installed with < RHEL 7.5) and file system hierarchy is split (e.g. /usr, /var, /var/log, ...), it's not possible to upgrade to RHEL 8.2 unless /var file system hosting /var/lib/leapp is extended by several Gigabytes.
This is not acceptable since XFS file systems can be shrinked once extended afterwards.
Example:
Customer has /, /usr, /var, /var/log, /opt which is very common when sticking to STIG recommendations.
These 5 file systems will require an additional 5 x 2GB (LEAPP_OVL_SIZE) = 10GB on /var to host the temporary disk images.
Now say 2GB LEAPP_OVL_SIZE is not sufficient due to having many packages (e.g. "Server with GUI" installation was used), consuming a lot of space in /usr.
With LEAPP_OVL_SIZE enlarged to 4GB (our usual recommendation), up to 20GB additional space on /var must be needed to host the temporary disk images.
There are multiple solutions to this issue:
Solution 1: be able to specify LEAPP_OVL_SIZE variable per XFS file system (some file systems do not require much disk image)
This solution would be suitable when Volume Group has not much free space and /var cannot be extended much more.
Solution 2: create a temporary file system mounted on /var/lib/leapp to host the disk images
This solution would be suitable when Volume Group / local disk has enough free space to hold a new volume until the upgrade is completed.
The customer can then trash the temporary file system once upgrade finished.
The original solution has been redesigned and should be fixed by upstream PR:
https://github.com/oamg/leapp-repository/pull/1097
All created OVL images are represented by sparse-files now. All systems originally affected by this ticket will consume just a fraction of original requriements - approx 128 MB per partition/volume specified in fstab. This value could be possibly yet lowered, but for now let's go with this.
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 (leapp and leapp-repository bug fix and enhancement update), 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-2023:7230