Bug 2166444
| Summary: | dnf needs-restarting always true from RHEL 8.5 on ppc64le | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Bernd Finger <bfinger> | |
| Component: | dnf-plugins-core | Assignee: | David Cantrell <dcantrell> | |
| Status: | VERIFIED --- | QA Contact: | swm-qe | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | high | |||
| Version: | 8.6 | CC: | abezhani, dstreit, james.antill, mbanas, nsella, pkratoch, rmeggins, than | |
| Target Milestone: | rc | Keywords: | AutoVerified, Triaged | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | dnf-plugins-core-4.0.21-21.el8 | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 2182157 (view as bug list) | Environment: | ||
| Last Closed: | Type: | Bug | ||
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 2182157 | |||
I ran more tests and found: I rebooted the RHEL 8.5 and RHEL 8.7 ppc64le systems several days after the problem occurred and then the output of "dnf needs-restarting -r" was: ---> No core libraries or services have been updated since boot-up. Reboot should not be necessary. <--- So it's probably worth testing again, with more reboots right after the initial reboot. I have confirmed this fix resolves the problem on ppc64le: https://github.com/rpm-software-management/dnf-plugins-core/pull/484 Based on comments, I assume this also works for aarch64 and s390x. I did also confirm it on x86_64. This is for RHEL-8, but a comment above notes this bug affects RHEL-9 as well so we should do an update there too. Should we clone this bug for RHEL-9? This is the commit to apply to dnf-plugins-core for RHEL-8: eb0a223c84d4a065ec7b54faa28679d88aef559d https://github.com/rpm-software-management/dnf-plugins-core (In reply to David Cantrell from comment #8) > This is the commit to apply to dnf-plugins-core for RHEL-8: > > eb0a223c84d4a065ec7b54faa28679d88aef559d > https://github.com/rpm-software-management/dnf-plugins-core Strike this comment, this is the fix to apply to dnf-plugins-core for RHEL-8: https://github.com/rpm-software-management/dnf-plugins-core/pull/468/commits/b8132e1e04fb44c9ef8ab7dbcea2d2b3b920be2c To verify the fix, follow the steps to reproduce in the opening comment. On step 6 you should get 0 back from the "dnf needs-restarting -r" command. |
Description of problem: After updating the RHEL 8 kernel ("dnf update kernel") of a ppc64le system and rebooting, the "needs-restarting -r" or "dnf needs-restarting -r" commands indicate that a reboot is required and the return code of these commands is 1. Version-Release number of selected component (if applicable): RHEL 8.5, 8.6 or 8.7 on platform ppc64le How reproducible: always Steps to Reproduce: 1. Install RHEL 8.5, 8.6 or 8.7 on platform ppc64le. 2. Run "needs-restarting -r" (The return code is 0, as expected). 3. Run "dnf update kernel -y" to update the RHEL kernel. 4. Run "needs-restarting -r" again (The return code is 1, as expected). 5. Reboot the system. 6. Log in and run "needs-restarting -r" again (The return code is still 1 but must be 0. See below for more details). Actual results: At step 6, the return code is 1 and the output will be similar to: ---> Updating Subscription Management repositories. Core libraries or services have been updated since boot-up: * dbus * dbus-daemon * kernel * linux-firmware * systemd Reboot is required to fully utilize these updates. More information: https://access.redhat.com/solutions/27943 <--- Expected results: At step 6, the return code is 0 and the output is: ---> No core libraries or services have been updated since boot-up. Reboot should not be necessary. <--- Additional info: I repeated the "Steps to Reproduce" on RHEL 8.6 on x86, s390x and aarch64. On these 3 hardware platforms, after a reboot following a RHEL kernel update, the return code of "needs-restarting -r" is 0, as expected. Note: https://bugzilla.redhat.com/show_bug.cgi?id=2137935 has a similar summary and description but by testing "stat -c %y /proc/1" which shows the root cause for that bug, I can confirm that the root cause in my case is different. In other words, the output of this stat command is similar to that on not affected systems, and the output of the "uptime" command is as expected on all the systems I tested.