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.
Bug 1870813 - leapp upgrade fails when filesystems are mounted with nobarrier option but doesn't warn in preupgrade check
Summary: leapp upgrade fails when filesystems are mounted with nobarrier option but do...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: leapp-repository
Version: 7.8
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Leapp team
QA Contact: Alois Mahdal
URL:
Whiteboard:
Depends On:
Blocks: 1818077 1818088
TreeView+ depends on / blocked
 
Reported: 2020-08-20 19:29 UTC by Lark Gordon
Modified: 2024-06-13 22:58 UTC (History)
6 users (show)

Fixed In Version: leapp-repository-0.13.0-1.el7_9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-16 08:59:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 5904261 0 None None None 2021-03-24 21:44:01 UTC

Comment 5 Petr Stodulka 2021-01-29 15:53:30 UTC 
Just update, the upstream PR inhibiting the upgrade when removed/obsoleted XFS mount options are present is here
    https://github.com/oamg/leapp-repository/pull/639
Comment 6 Eric Sandeen 2021-02-02 14:03:54 UTC 
It seems that it would be preferable to simply remove the "nobarrier" option during upgrade rather than halting upgrade, because this "tunable" is now automatically selected internally by the kernel - this is the proper thing for an administrator to do, given the details of the changes.

I'm not sure what the rules or parameters for LEAPP are, perhaps it is policy to halt on anything like this.

But in this case it would truly be safe to manually remove the "nobarrier" option and proceed with the upgrade.
Comment 8 Petr Stodulka 2021-02-02 15:02:43 UTC 
Hi Eric, the current solution is the most probably temporary - without a promise. We have already even a PoC PR trying to migrate the fstab during the upgrade, but we are not able to deliver it in the upcoming build. To prevent people to hit this issue, we rather inhibit the upgrade for now. Of course, users can update the fstab manually prior the upgrade (and it's expected they will do it) so they are able to do the upgrade still. Just the manual update of the fstab is required before the upgrade.
Comment 15 errata-xmlrpc 2021-02-16 08:59:00 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-2021:0569
Note You need to log in before you can comment on or make changes to this bug.