Bug 1662858
| Summary: | Please update edac-utils to version 0.18 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Ole Holm Nielsen <ole.h.nielsen> |
| Component: | edac-utils | Assignee: | Aristeu Rozanski <arozansk> |
| Status: | CLOSED ERRATA | QA Contact: | Jiri Dluhos <jdluhos> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.6 | CC: | arozansk, fedora, jbastian, mgrondona, woodard |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | edac-utils-0.16-16.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-06 12:44:07 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: | 1656539 | ||
|
Description
Ole Holm Nielsen
2019-01-02 08:51:00 UTC
See bz #1277443. If we can get it into Fedora, eventually it'll be in RHEL. Is that github link the official upstream for edac-utils now? Is 0.18 really from many years ago? (In reply to Trevor Cordes from comment #5) > See bz #1277443. If we can get it into Fedora, eventually it'll be in RHEL. We need the updated edac-utils in RHEL7 today, thanks a lot! We want to run edac-util on our production servers to monitor their health. Fedora is not going to go onto our production servers. Future RHEL versions (8?) is unfortunately not helping us today. > Is that github link the official upstream for edac-utils now? Is 0.18 > really from many years ago? Yes, it seems so. The edac-utils author is apparently Mark Grondona <mgrondona>, see https://github.com/grondo/edac-utils/blob/master/AUTHORS It's amazing that the update to 0.18 wasn't made years ago, but better late than never! Hopefully the update 0.16->0.18 will be a simple one, given that only minor changes were introduced. Yes, edac-utils was replaced by rasdaemon for quite a while. All new development happens there. Thanks a lot, I should take a closer look at rasdaemon! Since edac-utils is already in RHEL7, perhaps we can propose to pull back the trivial patch they need or update to 0.18, just to give the user more time to move to rasdaemon. The commit in question is here: https://github.com/grondo/edac-utils/commit/c29b14d0d07184bd2d250bf355a1dee6faa47572 in case it is helpful. That's what I did. Only backported the patch to fix the issue with --quiet. (In reply to Aristeu Rozanski from comment #11) > That's what I did. Only backported the patch to fix the issue with --quiet. Thanks! Wow, I had never heard of rasdaemon, and I do a lot of linux reading and searching around for ECC details. Thanks for that tidbit of info. I'm using rasdaemon now. The sqlite db aspect sounds like a really good idea. Docs aren't so hot though. For other people to find it in the future, perhaps a note in the edac-utils man page saying it's superseded by rasdaemon would be useful. Thanks so much for the useful tip. I'll share it with all my ECC buddies. (In reply to Trevor Cordes from comment #13) > Wow, I had never heard of rasdaemon, and I do a lot of linux reading and > searching around for ECC details. Thanks for that tidbit of info. I'm > using rasdaemon now. The sqlite db aspect sounds like a really good idea. > Docs aren't so hot though. Did you see the rasdaemon docs in https://pagure.io/rasdaemon ? Confirming that the new package contains the fix, functionally. # RHEL7.6 before installing new edac-utils (have edac-utils-0.16-15.el7) $ edac-util --quiet edac-util: No errors to report. # new version downloaded $ rpm -U edac-utils-0.16-16.el7.x86_64.rpm $ edac-util --quiet $ VERIFIED. :-) 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. https://access.redhat.com/errata/RHBA-2019:2095 |