Bug 1020584

Summary:	rasdaemon systemd unit points incorrect path
Product:	[Fedora] Fedora	Reporter:	Kazuo Moriwaka <kmoriwak>
Component:	rasdaemon	Assignee:	Mauro Carvalho Chehab <mchehab>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	mchehab, tomek
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:	2015-01-15 10:28:55 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 Kazuo Moriwaka 2013-10-18 03:07:03 UTC

Description of problem:

rasdaemon.service file contains incorrect path for ExecStart and it cannot start.

Version-Release number of selected component (if applicable):

rasdaemon-0.4.1-3.fc19.x86_64

Details:

In /usr/lib/systemd/system/rasdaemon.service
----------------------
[Unit]
Description=RAS daemon to log the RAS events
After=syslog.target

[Service]
ExecStart=/usr/local/sbin/rasdaemon -f     <======= here
Restart=on-abort
----------------------

Comment 1 Fedora End Of Life 2015-01-09 20:17:14 UTC

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Tomasz Torcz 2015-01-15 10:28:55 UTC

Fixed upstream in 4bfa45f56e1500f1cfc8de3fd8d1228b11011e95, which is present in 0.5.1 packaged for Fedora.