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.
1. Proposed title of this feature request
[ RFE ] Improve the error message displayed by leapp when the conerned XFS filesystem is build with ftype=0 option.
2. What is the nature and description of the request?
Modofication of the backend code, so that Leapp can log more helpful information in the leapp-report file which is generally reviewed by the end users.
3. Why does the customer need this? (List the business requirements here)
When "leapp preupgrade" fails and shows this error in leapp-report:
Error Summary
-------------
Disk Requirements:
At least 1044MB more space needed on the / filesystem.
It usually suspected that we actually have some issue with disk space but neither disk space is filled up nor the inodes for the same filesystem. Then a bit googling gives us https://access.redhat.com/solutions/5057391 which explains, if the affected filesystem is build using ftype=0 option what happens and how to workaroud the issue.
Our goal is to give some more data in the error message that can explain if the issue is affected due to the "Generic case" or "XFS ftype=0 case" as explained in the KB, since users cannot always dive into debug logs to find out the messages related to "XFS ftype=0" situation.
4. How would the customer like to achieve this? (List the functional requirements here)
During "leapp preupgrade"
5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
NA
6. Is there already an existing RFE upstream or in Red Hat Bugzilla?
NA
7. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
As soon as possible
8. Is the sales team involved in this request and do they have any additional input?
A solution Architect is involved in the support case.
9. List any affected packages or components.
leapp
10. Would the customer be able to assist in testing this functionality if implemented?
Yes
11. Additional information:
In private notes of the BZ
After the discussion, we are reopenning this ticket to deliver a partial improvement in the meanwhile, before we will be able to deliver the proper solution:
* https://github.com/oamg/leapp-repository/pull/956
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:3187