Bug 2110045

Summary: [ RFE ] Improve the error message displayed by leapp when the concerned XFS filesystem is built with ftype=0 option
Product: Red Hat Enterprise Linux 7 Reporter: Sayan Das <saydas>
Component: leapp-repositoryAssignee: Leapp team <leapp-notifications>
Status: CLOSED ERRATA QA Contact: Upgrades and Supportability <upgrades-and-supportability>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.9CC: mmacura, pstodulk, vfeenstr
Target Milestone: rcKeywords: Reopened, Triaged
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: leapp-repository-0.18.0-1.el7_9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-17 15:00:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sayan Das 2022-07-22 20:50:43 UTC 
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
Comment 5 Petr Stodulka 2022-07-25 08:57:51 UTC 
This is duplicate of bug 1832730. Closing.

*** This bug has been marked as a duplicate of bug 1832730 ***
Comment 6 Petr Stodulka 2023-01-17 12:41:45 UTC 
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
Comment 13 errata-xmlrpc 2023-05-17 15:00:24 UTC 
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