Bug 2303185

Summary:	The Ipmievd Service File has a wrong PIDFile Entry
Product:	[Fedora] Fedora	Reporter:	Lukas Jung <jung>
Component:	ipmitool	Assignee:	Kevin Fenzi <kevin>
Status:	POST ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	jridky, jsafrane, kevin, pcahyna
Target Milestone:	---	Keywords:	Reopened
Target Release:	---	Flags:	pcahyna: mirror+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-06-08 16:01:05 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:

Description Lukas Jung 2024-08-06 15:18:29 UTC

The Unit File from the ipmievd Package (/usr/lib/systemd/system/ipmievd.service)
specifies a PIDFile Directive "PIDFile=/run/ipmievd.pid" and the options provided to the ipmievd binary inside /etc/sysconfig/ipmievd. one of those options is pidfile=/run/ipmievd.pid but the ipmievd manpage says that it appends a 0 per default to the pidfile. this causes the service to start ipmievd but timeout since its looking for /run/ipmievd.pid as pidfile but ipmievd creates /run/ipmievd.pid0




Reproducible: Always

Steps to Reproduce:
1.install ipmievd
2.start the ipmievd.service
3. observe a timeout failure
Actual Results:  
the service is unable to start

Expected Results:  
the service should start and report sel logs

my workaround was an systemd override that specifies the PIDFile as none and the service runs without a problem

Comment 1 Pavel Cahyna 2024-08-06 16:27:56 UTC

Oh yes, I fixed it in CentOS Stream, but forgot to submit the fix to Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=2100475

Comment 2 Kevin Fenzi 2024-12-21 19:18:00 UTC

I don't see a fix on the stream side here... 

Is this fixed? or still happening?

Comment 3 Aoife Moloney 2025-04-28 13:36:14 UTC

This message is a reminder that Fedora Linux 40 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '40'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 40 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Aoife Moloney 2025-05-20 19:19:55 UTC

Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13.

Fedora Linux 40 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 5 Pavel Cahyna 2025-11-11 18:45:04 UTC

Sorry, I was mistaken - I thought it was related to CentOS Stream bug bz2100475, but in fact it is a different problem. The problem is not that "it appends a 0 per default to the pidfile" - this should happen only when the default for pidfile is used, not if overriden on the command line. The problem is rather that the pidfile= argument is entirely ignored: if specified as "pidfile=/run/ipmievd.piii", the daemon still creates "/run/ipmievd.pid0" and not "pidfile=/run/ipmievd.piii0". This regression was introduced in the fix for https://github.com/ipmitool/ipmitool/issues/104 .

Comment 6 Fedora Release Engineering 2026-05-06 11:52:30 UTC

This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '42'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 42 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 7 Aoife Moloney 2026-06-08 16:01:05 UTC

Fedora Linux 42 entered end-of-life (EOL) status on 2026-05-27.

Fedora Linux 42 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.