Bug 819571
Summary: | Software updates fail when a redundant kernel removal isn't done first | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Matt |
Component: | apper | Assignee: | Rex Dieter <rdieter> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | hughsient, kevin, ltinkl, rdieter, smparrish |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-13 21:32:33 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: |
Description
Matt
2012-05-07 15:00:21 UTC
I am running both a 64 bit version of Fedora on one machine and a 32 bit version on another, both have the same update bug. Both can be solved by the same methods. I assume this same problem is reproducible using a simple: 'yum update' too, would be nice if you could verify that. If so... I believe removals are always done last, and I don't think there's any way around that design/policy decision. My only suggestion would be to consider reducing the default installonly_limit=3 in /etc/yum.conf to 2 I could be wrong, but iirc, the default /boot partition size since since (at least) f16 is supposed to be 500mb (In reply to comment #2) > I assume this same problem is reproducible using a simple: > 'yum update' > too, would be nice if you could verify that. If so... > > I believe removals are always done last, and I don't think there's any way > around that design/policy decision. > > My only suggestion would be to consider reducing the default > installonly_limit=3 > in /etc/yum.conf to 2 Hi, I just tried 'Yum update' on one of my other Fedora systems which also has 100 meg /boot partition and I found yum update had no problems at all. It also had to remove an old kernel but seems to have done it before it actually installed the new kernel, going by the output in the terminal, as it listed the removal of the old kernel before it listed it had installed the new kernel. I shall try the option to restrict old kernels and see how that goes the next time. It would be worth flagging that using 'yum-complete-transaction' as suggested by the error mesages when updater failed, can cause the transactions the command attempts to complete, to be re-run repeatedly untill Fedora gets tired and actually kills the process. And even after that, Fedora is left with hung transactions so updater or software manager won't initialise. I had that each time I ran 'yum-complete-transaction'. But eventually located the tip about using 'yum-complete-transaction --cleanup-only' instead, which after use allowed me to run software management and remove the old kernel. then run updater again. This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 'version' of '16'. 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 prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed. |