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 xfs partitions are bind mounted, leapp treats each one as an individual xfs partition. If we have ftype=0, then leapp assumes each one needs an overlay which increases the amount of space needed in /var/lib/leapp.
This customer had 12 xfs partitions, but only 2 were valid. The other 10 were bind mounts. Leapp reported that we needed 36GB (With a 3G OVL size) in /var/lib/leapp but upon reboot, only used 6-7 GB (as the bind mounts were not in the fstab so do not mount upon boot).
Version-Release number of selected component (if applicable):
leapp-0.15.0-2.el7_9.noarch
leapp-deps-0.15.0-2.el7_9.noarch
leapp-upgrade-el7toel8-0.17.0-10.el7_9.noarch
leapp-upgrade-el7toel8-deps-0.17.0-10.el7_9.noarch
python2-leapp-0.15.0-2.el7_9.noarch
How reproducible:
Everytime
Steps to Reproduce:
1. Have a system with ftype=0 on an xfs partition
2. bind mount any xfs partitions any number of times
3. leapp upgrade
Actual results:
====> * target_userspace_creator
Initializes a directory to be populated as a minimal environment to run binaries from the target system.
2023-04-27 10:24:27.525 ERROR PID: 12215 leapp.workflow.TargetTransactionFactsCollection.target_userspace_creator: Not enough space available for creating required disk images in /var/lib/leapp/scratch. Needed: 36864 MiB
Expected results:
We could base calculations off only whats in the fstab to avoid bind mounts.
Or a warning that # bind mounts are present and affecting this size estimate.
Additional info:
Lowering the priority as it's expected to be a corner case.
Comment 5RHEL Program Management
2023-09-12 13:22:14 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 6RHEL Program Management
2023-09-12 14:22:01 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.
Description of problem: When xfs partitions are bind mounted, leapp treats each one as an individual xfs partition. If we have ftype=0, then leapp assumes each one needs an overlay which increases the amount of space needed in /var/lib/leapp. This customer had 12 xfs partitions, but only 2 were valid. The other 10 were bind mounts. Leapp reported that we needed 36GB (With a 3G OVL size) in /var/lib/leapp but upon reboot, only used 6-7 GB (as the bind mounts were not in the fstab so do not mount upon boot). Version-Release number of selected component (if applicable): leapp-0.15.0-2.el7_9.noarch leapp-deps-0.15.0-2.el7_9.noarch leapp-upgrade-el7toel8-0.17.0-10.el7_9.noarch leapp-upgrade-el7toel8-deps-0.17.0-10.el7_9.noarch python2-leapp-0.15.0-2.el7_9.noarch How reproducible: Everytime Steps to Reproduce: 1. Have a system with ftype=0 on an xfs partition 2. bind mount any xfs partitions any number of times 3. leapp upgrade Actual results: ====> * target_userspace_creator Initializes a directory to be populated as a minimal environment to run binaries from the target system. 2023-04-27 10:24:27.525 ERROR PID: 12215 leapp.workflow.TargetTransactionFactsCollection.target_userspace_creator: Not enough space available for creating required disk images in /var/lib/leapp/scratch. Needed: 36864 MiB Expected results: We could base calculations off only whats in the fstab to avoid bind mounts. Or a warning that # bind mounts are present and affecting this size estimate. Additional info: