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 removing old kernel for example packagekit says that I should restart to complete my update .. this is wrong. 

Version-Release number of selected component (if applicable):
PackageKit-0.7.4-5.el7

How reproducible:
always

Steps to Reproduce:
1.execute 'pkcon remove old_installed_kernel'

  
Actual results:
pk says I should remove

Expected results:
as removal of running kernel is not allowed there should be no warning

Additional info:

Fixed upstream, good catch:

commit f35f3fd7319136111e177b5ec000034d95990ce1
Author: Richard Hughes <richard>
Date:   Mon Nov 5 12:35:49 2012 +0000

    yum: Don't rely on a blacklist for RequireRestart
    
    Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=850894

:100755 100755 c1106f2... 7e2d665... M  backends/yum/yumBackend.py

commit 1b7e29c9e6348fb7eed5dbf8c901a7550981bfa2
Author: Richard Hughes <richard>
Date:   Mon Nov 5 12:34:17 2012 +0000

    Emit RequireRestart(system) in a PackageKit daemon plugin
    
    This means the backends don't all have to do it themselves.

:100644 100644 f5f67f5... a029e73... M  backends/dummy/pk-backend-dummy.c
:100644 100644 f693c2c... 5e4ee74... M  src/plugins/Makefile.am
:000000 100644 0000000... 505234e... A  src/plugins/pk-plugin-require-restart.c