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.
Description of problem:
When a kernel-core dependency is targeted as the install, such as "yum install kernel-core-uname-r", dnf ignores the 3 kernel limit set by installonly_limit
Version-Release number of selected component (if applicable):
dnf-4.7.0-11.el8.noarch
libdnf-0.63.0-11.1.el8.x86_64
How reproducible:
Everytime
Steps to Reproduce:
1. Have 3 (less than latest version) kernel/kernel-cores installed
2. # yum install kernel-core-uname-r
3.
Actual results:
[root@r8 ~]# rpm -q kernel
kernel-4.18.0-372.26.1.el8_6.x86_64
kernel-4.18.0-372.32.1.el8_6.x86_64
kernel-4.18.0-425.3.1.el8.x86_64
[root@r8 ~]# rpm -q kernel-core
kernel-core-4.18.0-372.26.1.el8_6.x86_64
kernel-core-4.18.0-372.32.1.el8_6.x86_64
kernel-core-4.18.0-425.3.1.el8.x86_64
[root@r8 ~]# yum install kernel-core-uname-r
Installing:
kernel-core x86_64 4.18.0-425.10.1.el8_7 rhel-8-for-x86_64-baseos-rpms
Reinstalling:
kernel-core x86_64 4.18.0-372.26.1.el8_6 rhel-8-for-x86_64-baseos-rpms
[root@r8 ~]# rpm -q kernel
kernel-4.18.0-372.26.1.el8_6.x86_64
kernel-4.18.0-372.32.1.el8_6.x86_64
kernel-4.18.0-425.3.1.el8.x86_64
[root@r8 ~]# rpm -q kernel-core
kernel-core-4.18.0-372.32.1.el8_6.x86_64
kernel-core-4.18.0-425.3.1.el8.x86_64
kernel-core-4.18.0-425.10.1.el8_7.x86_64
kernel-core-4.18.0-372.26.1.el8_6.x86_64
Expected results:
only 3 kernel/kernel-cores should be installed at a time. The oldest one should be removed when a new kernel is installed.
Additional info:
This may potentially be the cause for https://bugzilla.redhat.com/show_bug.cgi?id=2163461
Thank you for the report, this is indeed a problem in dnf.
I would like to note though that we discourage installing just kernel-core this way. It will resulting in missing kernel-modules which might lead to a missing functionality on systems.
Comment 6RHEL Program Management
2023-08-15 07:27:41 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
This bug was migrated to our public Jira instance. From september this year we will stop using bugzilla for bug reporting againts RHEL related products.
The link to the jira bug can be found below:
https://issues.redhat.com/browse/RHEL-1253