Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
lm_sensors.service fails when no sensors found regardless being run in virtual or bare metal environment
Version-Release number of selected component (if applicable):
lm_sensors-3.4.0-22.20180522git70f7e08.el8
How reproducible:
Always
Steps to Reproduce:
1. install lm_sensors in virtual environment (with no passthrough devices configured)
2. start the service or reboot
3.
Actual results:
* lm_sensors.service - Hardware Monitoring Sensors
Loaded: loaded (/usr/lib/systemd/system/lm_sensors.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2021-01-08 14:37:56 PST; 36min ago
Process: 1207 ExecStart=/usr/bin/sensors -s (code=exited, status=1/FAILURE)
Process: 1168 ExecStart=/usr/libexec/lm_sensors/lm_sensors-modprobe-wrapper $BUS_MODULES $HWMON_MODULES (code=exited, status=
1/FAILURE)
Main PID: 1207 (code=exited, status=1/FAILURE)
Jan 08 14:37:55 pdlodb01 systemd[1]: Starting Hardware Monitoring Sensors...
Jan 08 14:37:55 pdlodb01 lm_sensors-modprobe-wrapper[1168]: No sensors with loadable kernel modules configured.
Jan 08 14:37:55 pdlodb01 lm_sensors-modprobe-wrapper[1168]: Please, run 'sensors-detect' as root in order to search for availab
le sensors.
Jan 08 14:37:56 pdlodb01 sensors[1207]: No sensors found! <<<----
Jan 08 14:37:56 pdlodb01 sensors[1207]: Make sure you loaded all the kernel drivers you need.
Jan 08 14:37:56 pdlodb01 sensors[1207]: Try sensors-detect to find out which these are.
Jan 08 14:37:56 pdlodb01 systemd[1]: lm_sensors.service: Main process exited, code=exited, status=1/FAILURE
Jan 08 14:37:56 pdlodb01 systemd[1]: lm_sensors.service: Failed with result 'exit-code'.
Jan 08 14:37:56 pdlodb01 systemd[1]: Failed to start Hardware Monitoring Sensors.
Expected results:
Less confusing Error message in Virt env where no sensors are expected, perhaps exit code 0
Additional info:
lm_sensors is pulled in as dependency by pcp-pmda-lmsensors after Bug 1790427 fix, so the errors are common for users having installed AppStream "performance" group.
ConditionVirtualization=!vm was refused in Bug 1781192
I commented in bz1781192, I think solving this via lmsensors might be
the cleanest thing to do. It would also fix things for customers who
by policy deploy one set of packages on both virtual and physical
systems.