Bug 1967245

Summary:	RFE: Implement global property DefaultDeviceTimeout and corresponding kernel command line parameter
Product:	Red Hat Enterprise Linux 8	Reporter:	Renaud Métrich <rmetrich>
Component:	systemd	Assignee:	David Tardon <dtardon>
Status:	CLOSED ERRATA	QA Contact:	Frantisek Sumsal <fsumsal>
Severity:	high	Docs Contact:
Priority:	high
Version:	8.4	CC:	apanagio, dtardon, jamacku, loberman, systemd-maint-list
Target Milestone:	rc	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	systemd-239-65.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-11-08 10:49:17 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 Renaud Métrich 2021-06-02 16:51:05 UTC

Description of problem:

Due to storage issue/slowness at boot, usually with multipath or 3rd party storage vendors, it's not rare that customers have to individually add x-systemd.device-timeout=XXX to all his entries in /etc/fstab, which is a real pain and prevents managing the systems easily.

I would hence love to have a DefaultDeviceTimeout property in /etc/systemd/system.conf and corresponding kernel command line parameter systemd.default_device_timeout (or similar, I'm not used to systemd parameters) that would enable to increase the delay waiting for devices.

For now, the only global property is DefaultTimeoutJobStartSec but it's definitely not suitable: we don't want to modify the behaviour for other components in the system.

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

All systemd releases, starting with RHEL7


How reproducible:

N/A

Comment 3 Plumber Bot 2022-08-18 11:56:26 UTC

fix merged to github master branch -> https://github.com/redhat-plumbers/systemd-rhel8/pull/305

Comment 7 errata-xmlrpc 2022-11-08 10:49:17 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-2022:7727