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:
After installing security errata for kernel, kernel-core, or kernel-modules, yum/dnf updateinfo will show the errata as still applicable. 

It shows them as both installed and available.


Version-Release number of selected component (if applicable):
libdnf-0.22.5-5.el8_0.x86_64

How reproducible:
Everytime

Steps to Reproduce:
1. yum updateinfo list kernel  < Something is available
2. yum update kernel
3. yum updateinfo list kernel

Actual results:
We still see the same errata because the lower version is still installed. Even a reboot to ensure the new kernel is in use doesn't change this behavior

Expected results:
The errata should be resolved and not available since it's already installed (This is how RHEL 7 works)

Additional info:

I created patch https://github.com/rpm-software-management/dnf/pull/1485 which should improve the behaviour of `dnf --available`. The new behaviour is:

1. yum updateinfo list kernel  < Something is available
2. yum update kernel
3. yum updateinfo list kernel < something is still available (because the running kernel remains in older version)
4. reboot with the newest kernel
5. yum updateinfo list kernel - nothing is printed

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:1823

*** Bug 1773923 has been marked as a duplicate of this bug. ***