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.
DescriptionBruno Goncalves
2014-02-10 08:53:24 UTC
Description of problem:
Trying to install a newer version of kernel that is more recent that the current used for booting and older than the newest version installed fail.
Transaction check error:
package kernel-3.10.0-84.el7.x86_64 (which is newer than kernel-3.10.0-71.el7.x86_64) is already installed
Version-Release number of selected component (if applicable):
yum-3.4.3-112.el7.noarch
How reproducible:
100%
Steps to Reproduce:
1.Install 3 kernel to a system
# rpm -q kernel
kernel-3.10.0-84.el7.x86_64
kernel-3.10.0-70.el7.x86_64
kernel-3.10.0-64.el7.x86_64
2.Boot to the second kernel
# uname -r
3.10.0-70.el7.x86_64
3.Try to install a kernel version higher than the current one and lower then the highest one.
Actual results:
Error will happen
package kernel-3.10.0-84.el7.x86_64 (which is newer than kernel-3.10.0-71.el7.x86_64) is already installed
Expected results:
kernel-3.10.0-64.el7.x86_64 version should be removed and kernel-3.10.0-84.el7.x86_64 should be installed
Um, AFAIR rpm has always behaved this way. The trick is not --force but --oldpackage (RPMPROB_FILTER_OLDPACKAGE) which is needed in this case, just like its needed in case of downgrade.
James, regression compared to what? Like said IIRC rpm has always behaved this way (that special oldpackage flag needed for old packages, whether install or something else), certainly RHEL-6 version does, as expected (just tested).
Never mind the needinfo, tested RHEL-5 and rpm behaves the same there.
Yum sets RPMPROB_FILTER_OLDPACKAGE as needed when the to-be-installed package is older than the *oldest* version of the same package, but rpm requires RPMPROB_FILTER_OLDPACKAGE for installing a version that is older than the *newest* version of installed package.
Back to yum.
Found the problem ... yum was seeing the older installed package version, and deciding it was an upgrade. Added testcase and fix upstream.
commit fada4b8dbd30d0335a9c07067a74dccec0abbedb
Author: James Antill <james>
Date: Mon Sep 29 11:40:54 2014 -0400
Don't look for upgrades for install only packages. BZ 1063181.
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://rhn.redhat.com/errata/RHBA-2015-0398.html