Bug 1302179
| Summary: | PRESETS: enable mcelog by default | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Zbigniew Jędrzejewski-Szmek <zbyszek> |
| Component: | fedora-release | Assignee: | Dennis Gilmore <dennis> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 24 | CC: | dennis, jdisnard, kevin, pbrobinson, sgallagh, zbyszek |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-03-29 12:11:32 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
Zbigniew Jędrzejewski-Szmek
2016-01-27 03:23:22 UTC
Zbigniew, when making requests like this, can you please provide the following information: * Does the service require post-rpm-installation configuration in order to be useful (for example, does it need manual edits to a configuration file)? * Does the service listen on a network socket for connections originating on a separate physical or virtual machine? * Is the service non-persistent (i.e. run once at startup and exit)? Based on those answers, we can determine whether I should just go ahead and apply the preset or file a FESCo ticket for approval first. mcelog is a utility that collects and decodes Machine Check Exception data on x86-32 and x86-64 systems. (In reply to Stephen Gallagher from comment #1) > * Does the service require post-rpm-installation configuration in order to > be useful (for example, does it need manual edits to a configuration file)? No, out of the box it just logs events, which is what we want. > * Does the service listen on a network socket for connections originating on > a separate physical or virtual machine? It listens on a UNIX socket. > * Is the service non-persistent (i.e. run once at startup and exit)? Persistent. > Based on those answers, we can determine whether I should just go ahead and > apply the preset or file a FESCo ticket for approval first. It meets the criteria to be enabled without going through FESCo. Submitted as pull-requests to the fedora-release package. * https://pagure.io/fedora-release/pull-request/22 (Rawhide/F24) * https://pagure.io/fedora-release/pull-request/23 (F23) This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions |