Bug 463447
Summary: | If yum gets an exception in it's rpm callbacks ... rpm can go insane killing the machine | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | James Antill <james.antill> |
Component: | yum | Assignee: | James Antill <james.antill> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 5.2 | CC: | ddumas, jhutar, syeghiay |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-01-20 21:43:52 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
James Antill
2008-09-23 15:00:33 UTC
So I spoke with Panu and he seems to think we really should get this in for 5.3, so flags? Note that where Panu put that raise is not protected by the yum patch, because it's not possible for an IO exception to occur there. I tried to simulate this by using: (yum update -y | cat) & ...and then kill'ing the cat command at various points ... and while that did do some "interesting" things, including just halting the transaction immediately, it didn't do the "rpm erases the system" problem. But that should be mostly ignored after the latest patch (yum/rpm should continue). An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0176.html |