Bug 1488524
Summary: | dnf needs-restarting fails to operate | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Steven Haigh <netwiz> |
Component: | dnf-plugins-core | Assignee: | rpm-software-management |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 29 | CC: | dmach, jmracek, mluscon, netwiz, packaging-team-maint, rpm-software-management, vmukhame |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-11-27 23:04:10 UTC | 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: | 1491190 |
Description
Steven Haigh
2017-09-05 15:31:13 UTC
As a side note, I'm not sure if this has ever worked - as I don't recall ever getting any output from this plugin. I use the yum-utils version of 'needs-restarting' on RHEL servers all the time. Not sure if it ever worked either... Can you actually try to use tracer plugin from dnf-plugins-extras? That seems to be better. I did look at the tracer plugin - but it didn't seem to be quite what I was after. I'm not sure that it shows 'after the fact' applications that are out of date - say that they were installed via dnfdragora or packagekit. Sadly, I can't test at the moment due to the fedora site being dead. Interestingly enough, I just ran a 'dnf -y update' on my system which pulled down a heap of packages. I then got: # dnf needs-restarting 1120 : /usr/bin/sddm 1231 : /usr/libexec/sddm-helper --socket /tmp/sddm-auth8d73ce4b-97bc-4635-b8d4-4ed1f2a14b58 --id 1 --start /usr/bin/startkde 1309 : /usr/libexec/kf5/klauncher --fd=9 1313 : kded5 [kdeinit5] 1325 : /usr/bin/kaccess 1334 : /usr/bin/ksmserver 1346 : /usr/bin/kglobalaccel5 1356 : kwin_x11 1360 : /usr/libexec/kdeconnectd 1361 : /usr/bin/krunner 1363 : /usr/bin/plasmashell --- snip --- This is interesting - as: 1) it took a *lot* longer to run than any other time it has run (expected if its actually doing something); and 2) It actually output information. This is a first - so I'm not sure what the fix was - or how to try and replicate an issue again :\ This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'. This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |