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 1788851 - Upgrade fails as soon as 2 kernel-devel packages are installed on the system
Summary: Upgrade fails as soon as 2 kernel-devel packages are installed on the system
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: leapp-repository
Version: 7.7
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Leapp team
QA Contact: Alois Mahdal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-08 09:00 UTC by Renaud Métrich
Modified: 2023-03-24 16:39 UTC (History)
5 users (show)

Fixed In Version: leapp-repository-0.10.0-2.el7_8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-29 01:45:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 4723671 0 None None None 2020-01-08 15:06:31 UTC
Red Hat Product Errata RHBA-2020:1959 0 None None None 2020-04-29 01:46:15 UTC

Description Renaud Métrich 2020-01-08 09:00:50 UTC
Description of problem:

When 2 or more kernel-devel packages are installed on the system being upgraded, the "leapp upgrade" command fails, e.g.:

-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
# yum -y install kernel-devel-3.10.0-957.38.3.el7.x86_64 kernel-devel-3.10.0-957.41.1.el7.x86_64

# leapp upgrade
[...]

 Problem 1: problem with installed package kernel-devel-3.10.0-957.41.1.el7.x86_64
  - cannot install the best update candidate for package kernel-devel-3.10.0-957.41.1.el7.x86_64
  - cannot install both kernel-devel-4.18.0-147.3.1.el8_1.x86_64 and kernel-devel-3.10.0-957.41.1.el7.x86_64
  - cannot install both kernel-devel-4.18.0-147.3.1.el8_1.x86_64 and kernel-devel-3.10.0-957.38.3.el7.x86_64
 Problem 2: problem with installed package kernel-devel-3.10.0-957.38.3.el7.x86_64
  - cannot install the best update candidate for package kernel-devel-3.10.0-957.38.3.el7.x86_64
  - cannot install both kernel-devel-4.18.0-147.3.1.el8_1.x86_64 and kernel-devel-3.10.0-957.41.1.el7.x86_64
  - cannot install both kernel-devel-4.18.0-147.3.1.el8_1.x86_64 and kernel-devel-3.10.0-957.38.3.el7.x86_64
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------


Version-Release number of selected component (if applicable):

leapp-repository-0.9.0-4.el7.noarch


How reproducible:

Always, see above example.

Comment 2 Petr Stodulka 2020-01-08 11:19:16 UTC
We should probably report this as KI. Current recommended workround is to remove all older kernel-devel rpms (expecting that system is booted in the newest kernel) and run leapp again.

Comment 7 Alois Mahdal 2020-04-27 18:29:00 UTC
VERIFIED with

      - leapp-0.10.0-2.el7_8
      - leapp-repository-0.10.0-2.el7_8

Comment 9 errata-xmlrpc 2020-04-29 01:45:58 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, 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-2020:1959


Note You need to log in before you can comment on or make changes to this bug.