Bug 545760
| Summary: | broken trigger in acpid update | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Stephan Wiesand <stephan.wiesand> |
| Component: | acpid | Assignee: | Jiri Skala <jskala> |
| Status: | CLOSED ERRATA | QA Contact: | qe-baseos-daemons |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.5 | CC: | aglotov, atodorov, azelinka, cward, ilmis, jonas.courteau, kbsingh, ovasik, pkovar, rvokal, syeghiay, tao, thoger, tis |
| Target Milestone: | rc | Keywords: | Regression, ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
The acpid package contains a trigger scriptlet that returns a non-zero exit code if the /var/log/acpid log file does not exist. Prior to this update, if the acpid daemon was installed but never started on the system and the /var/log/acpid file did not exist, the scriptlet did not function properly and caused the package update process to fail, which could have resulted in two different acpid packages being installed on the system and registered with the RPM database (rpmdb). With this update, the acpid package has removed the spurious acpid record from rpmdb so that the problem is now fixed.
|
Story Points: | --- |
| Clone Of: | CVE-2009-4033, CVE-2009-4235 | Environment: | |
| Last Closed: | 2011-12-06 19:32:30 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 548374 | ||
|
Description
Stephan Wiesand
2009-12-09 10:13:45 UTC
A fairly obvious instructions to clean this up if that occurred, that may be useful to those that come across this bug. You can remove old package manually using rpm or yum and providing full NVR, not only package name. Get list of installed acpid packages: # rpm -q acpid acpid-1.0.4-9.el5 acpid-1.0.4-9.el5_4.1 Remove old one (acpid-1.0.4-9.el5) using rpm or yum: # rpm -e acpid-1.0.4-9.el5 or # yum erase acpid-1.0.4-9.el5 If you don't need to run acpid, it can be uninstalled completely. *** Bug 545710 has been marked as a duplicate of this bug. *** I vote against decision not to fix this issue. Fix is very simple and only requires new release of package with fixed script. This is clearly a bug in package and needs fixing. Rpm scripts can't just fail. I vote for fixing this. Going through every xen-virtual server by hand is not much fun. Agreed - this is causing our config management stuff to error out due to the error status returned by yum when installing this package on new installs. Only to explain comment https://bugzilla.redhat.com/show_bug.cgi?id=545710#c5 which brought some confusion here... that bugzilla got rejected because of the process reasons - not because the fix is not planned. So don't worry, the bug is planned to be fixed. This issue was fixed swiftly back then, and this bz should probably be "closed errata".
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
The acpid package contains a trigger scriptlet that returns a non-zero exit code if the /var/log/acpid log file does not exist. Prior to this update, if the acpid daemon was installed but never started on the system and the /var/log/acpid file did not exist, the scriptlet did not function properly and caused the package update process to fail, which could have resulted in two different acpid packages being installed on the system and registered with the RPM database (rpmdb). With this update, the acpid package has removed the spurious acpid record from rpmdb so that the problem is now fixed.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1786.html |