Bug 1901440
| Summary: | leapp upgrade fails in reboot phase when /boot is merged into / on zVM | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Renaud Métrich <rmetrich> | ||||||
| Component: | leapp-repository | Assignee: | Leapp team <leapp-notifications> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | smitterl | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 7.9 | CC: | cbesson, dhorak, fkrska, held, pstodulk, smitterl | ||||||
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| 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: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1818077, 1818088 | ||||||||
| Attachments: |
|
||||||||
|
Description
Renaud Métrich
2020-11-25 08:43:53 UTC
Created attachment 1733301 [details]
Proposal (minimal, doesn't handle "leapp upgrade" retries on failure)
The fix will be delivered via the PR:
https://github.com/oamg/leapp-repository/pull/634
Currently, it will fix this one particular issue. More generic fix for additional corner-cases will be delivered separately in future.
The fix mentioned above is causing additional issues in case of s390x machine. Regarding the urgency of the problem we have discovered to inhibit the upgrade (for now) for s390x machines when /boot is part of the rootfs: - https://github.com/oamg/leapp-repository/pull/641 Renaud, do you want to keep this BZ opened until the upgrade for such machines is possible or is the current fix ok for this particular BZ? (both works for me) Hi Petr, Please keep the BZ open until we have a real fix, we will need a fix anyway. Renaud. The same problem was detected meanwhile on RHEL-8.7 (see https://bugzilla.redhat.com/show_bug.cgi?id=2129716). Could you please provide a fix which works for s390x machines. IIUC, we have a draft fix for this upstream - https://github.com/oamg/leapp-repository/pull/991 but we didnt' have time to test this yet. If somebody has the opportunity to test this before we can, the build is available at https://copr.fedorainfracloud.org/coprs/g/oamg/leapp/repo/epel-7/group_oamg-leapp-epel-7.repo where $basearch must be substituted by x86_64 (even on s390x) # yum install "leapp-upgrade*pr991*" Installs the package. We have positive test results from IBM. Merging the PR in upstream. The fix will be part of the next build: * https://github.com/oamg/leapp-repository/pull/991 This BZ is expected to be testing in cooperation with IBM. We have already positive feedback from upstream pre-testing. The analogical bug 2129716 is going to be tested for RHEL 8 where the very same fix is going to be delivered too. It looks to me like the fixed in Version leapp-repository-0.17.0-5.el7_9 is wrong, Petr? Hi Sebastian, it should be correct, but I forgot to update the release in the erratum - if you refer to that - thanks for the ping. It should be fixed now. Let me know if there is a different problem. I am sorry for the mistake - too much tickets & processes. The final build will contain bumped release (0.18.0). corr: s/bumped release/bumped version/ The package is not yet in the latest EXTRA repo, I'll check some other day. Confirmed with leapp-repository-0.17.0-5.el7_9 and /boot a mere folder on / that upgrade 7->8 succeeded (--no-rhsm). The fix has been dropped in leapp-repository-0.17.0-9.el7_9 due to unplanned async release and will be added back after the rebase. Versions: leapp data https://github.com/oamg/leapp-repository/tree/32dc6b0ee9f2d91af1f3406b567e1237ac6d0769/etc/leapp/files (when using the official tar.gz leapp-data-21 I get an error) leapp-upgrade-el7toel8-0.18.0-1.el7_9.noarch I fail to finish preupgrade --no-rhsm. Error: Stderr: Host and machine ids are equal (9a34b694ac454a9e88d9a98004c2cb1e): refusing to link journals Failed to synchronize cache for repo 'baseos8', ignoring this repo. Failed to synchronize cache for repo 'appstream8', ignoring this repo. Error: Unable to find a match: dnf dnf-command(config-manager) I believe the "Host and machine..." can be ignored. Also, I believe the "Error: Unable to find match..." would be fixed if the caches for the RHEL 8 repos could be sync'd. I checked and the repos in our leapp_upgrade_repositories.repo file look correct to me. Petr, please can you help? Nevermind, my custom repositories had https urls. After changing to http everything works now. Verified leapp data https://github.com/oamg/leapp-repository/tree/32dc6b0ee9f2d91af1f3406b567e1237ac6d0769/etc/leapp/files leapp-upgrade-el7toel8-0.18.0-1.el7_9.noarch 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 |