Bug 2042340 - kernel-tools does not perform a daemon reload when installed/upgraded [NEEDINFO]
Summary: kernel-tools does not perform a daemon reload when installed/upgraded
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kernel
Version: 7.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Radomir Vrbovsky
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-19 09:46 UTC by Daniel Juarez
Modified: 2023-07-19 07:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-19 07:28:13 UTC
Target Upstream Version:
Embargoed:
dhoward: needinfo? (rvrbovsk)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2042424 1 unspecified CLOSED kernel-tools does not perform a daemon reload when installed/upgraded 2023-06-08 08:08:05 UTC
Red Hat Issue Tracker RHELPLAN-108676 0 None None None 2022-01-19 09:53:38 UTC

Internal Links: 2042424

Description Daniel Juarez 2022-01-19 09:46:55 UTC
With a recent upgrade of the kernel-tools package we see the following.

root@testnode ~]# systemctl status cpupower.service
● cpupower.service - Configure CPU power related settings
Loaded: loaded (/usr/lib/systemd/system/cpupower.service; disabled; vendor preset: disabled)
Active: inactive (dead)
Warning: cpupower.service changed on disk. Run 'systemctl daemon-reload' to reload units.

There seems to be no `systemctl daemon-reload`in the RPM scriptlet of this package.

In the %post part of the corresponding specfile there seems to miss a daemon reload, just where the following is specified:

```
%if %{with_tools}
	
%post -n kernel-tools
	
/sbin/ldconfig
```

Comment 7 RHEL Program Management 2023-07-19 07:28:13 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


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