Bug 1302179 - PRESETS: enable mcelog by default
Summary: PRESETS: enable mcelog by default
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-release
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dennis Gilmore
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-27 03:23 UTC by Zbigniew Jędrzejewski-Szmek
Modified: 2016-03-29 12:11 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-29 12:11:32 UTC
Type: Bug


Attachments (Terms of Use)

Description Zbigniew Jędrzejewski-Szmek 2016-01-27 03:23:22 UTC
Description of problem:
mcelog was enabled by default (using hardcoded systemctl enable). It was updated to use presets, but should still be started by default. It is ExclusiveArch: i686 x86_64.

Comment 1 Stephen Gallagher 2016-01-27 13:20:30 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.

Comment 2 Zbigniew Jędrzejewski-Szmek 2016-01-27 13:36:00 UTC
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.

Comment 3 Stephen Gallagher 2016-01-27 16:52:18 UTC
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)

Comment 4 Jan Kurik 2016-02-24 14:21:10 UTC
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

Comment 5 Mike McCune 2016-03-28 22:27:32 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions


Note You need to log in before you can comment on or make changes to this bug.