Bug 2042034

Summary:	exchange-bmc-os-info requires unknown ipmi.service
Product:	Red Hat Enterprise Linux 8	Reporter:	François Rigault <frigo>
Component:	ipmitool	Assignee:	Pavel Cahyna <pcahyna>
Status:	CLOSED MIGRATED	QA Contact:	Laura Trivelloni <ltrivell>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	8.4	CC:	rvr
Target Milestone:	rc	Keywords:	MigratedToJIRA, Triaged
Target Release:	---	Flags:	pm-rhel: 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:	2023-09-21 22:08:06 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 François Rigault 2022-01-18 17:47:51 UTC

Description of problem:
exchange-bmc-os-info requires unknown ipmi.service

Version-Release number of selected component (if applicable):
exchange-bmc-os-info-1.8.18-17.el8.noarch

How reproducible:
all the time:

Steps to Reproduce:
1. dnf install exchange-bmc-os-info
2. systemctl enable --now exchange-bmc-os-info
3.

Actual results:
Failed to start exchange-bmc-os-info.service: Unit ipmi.service not found.


Expected results:
should start fine

Additional info:


$ systemctl cat exchange-bmc-os-info
# /usr/lib/systemd/system/exchange-bmc-os-info.service
[Unit]
Description=Exchange Information between BMC and OS
After=ipmi.service network.target
Requires=ipmi.service

~~

I don't know what this ipmi.service is for (also there should be no dependency on the network). There is no suggestion/recommendation for this package and no man page. However removing the ipmi.service dependency seems to work fine.

Is it possible to remove the ipmi.service dependency, or to document which package provides it? (if any)

Comment 1 Pavel Cahyna 2022-01-18 18:25:02 UTC

This service is provided by OpenIPMI:
$ rpm -qf /usr//lib/systemd/system/ipmi.service 
OpenIPMI-2.0.31-3.el8.x86_64

Not sure why/if it is needed or how it interacts with the other stuff yet.

Comment 2 Pavel Cahyna 2022-01-18 18:33:01 UTC

And apparently ipmi.service is there to make sure that the ipmi modules are loaded. exchange-bmc-os-info.service needs the ipmi modules, so it makes sense to require this service, although I don't know whether it is still valid - it is possible that the modules get autoloaded nowadays without the need for this helper.

Comment 3 François Rigault 2022-01-18 19:06:28 UTC

oh, ok. indeed things could be improved a bit, but it works fine with the OpenIPMI package, thanks for the help :) I guess this can be closed.

Comment 4 Pavel Cahyna 2022-01-18 20:14:10 UTC

Let me keep it open as a reminder. If I have time, I will investigate in more detail the actual need for this. If not, I will at least add a RPM dependency on OpenIPMI to this subpackage when there is some more important update, as its absence is clearly a bug.

Comment 6 RHEL Program Management 2023-09-21 21:31:42 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 7 RHEL Program Management 2023-09-21 22:08:06 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.