Bug 2126819

Summary: systemd watchdogdevice not honored
Product: Red Hat Enterprise Linux 9 Reporter: Pat Riehecky <riehecky>
Component: systemdAssignee: systemd-maint
Status: CLOSED ERRATA QA Contact: Frantisek Sumsal <fsumsal>
Severity: medium Docs Contact:
Priority: medium    
Version: CentOS StreamCC: bstinson, dtardon, jamacku, jwboyer, systemd-maint-list, vagrawal
Target Milestone: rcKeywords: Bugfix, Reproducer, TestOnly, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: systemd-252-3.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-09 08:21:58 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:
Bug Depends On: 2138081    
Bug Blocks:    

Description Pat Riehecky 2022-09-14 13:37:21 UTC
Description of problem:
When WatchdogDevice=/dev/watchdog systemd still attempts to open /dev/watchdog0.  For reasons I don't understand, my host doesn't have /dev/watchdog0.

As a result, the watchdog is not initialized or managed by systemd.

Version-Release number of selected component (if applicable):
systemd-250-11.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Set WatchdogDevice=/dev/watchdog
2. reboot
3. if system doesn't have /dev/watchdog0 the watchdog is not initialized
4. if system has /dev/watchdog0, it is used instead of /dev/watchdog

Actual results:
The WatchdogDevice setting isn't honored.

Expected results:
The config option should be honored

Additional info:
https://github.com/systemd/systemd/pull/24664

Comment 4 errata-xmlrpc 2023-05-09 08:21:58 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (systemd bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2531