Bug 1854816

Summary:	Some block devices are not visible to the [disk] plugin.
Product:	Red Hat Enterprise Linux 8	Reporter:	Jiří Mencák <jmencak>
Component:	tuned	Assignee:	Jaroslav Škarvada <jskarvad>
Status:	CLOSED ERRATA	QA Contact:	Robin Hack <rhack>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.3	CC:	bnater, jeder, jskarvad, vagrawal
Target Milestone:	rc	Keywords:	Patch, TestCaseNeeded, Triaged, Upstream
Target Release:	8.4	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tuned-2.18.0-0.1.rc1.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2045919 (view as bug list)		Environment:
Last Closed:	2022-05-10 15:31:16 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:
Bug Blocks:	2045919

Description Jiří Mencák 2020-07-08 09:51:17 UTC

Description of problem:
While verifying tuned daemon functionality on a two systems I've noticed the [disk] plugin is not able to adjust tuning for some block devices.  In my case these were a DVD-ROM and an NVMe drive.

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

How reproducible:
Always

Actual results:
Unability to use the [disk] plugin to set properties such as IO disk elevator on devices such as NVMe drives.

Expected results:
Review the [disk] plugin and have the ability to use it to set the tuning where it makes sense.

Additional info:
https://github.com/redhat-performance/tuned/issues/101#issuecomment-394626316

Comment 3 Jaroslav Škarvada 2021-11-02 15:43:37 UTC

I think it's bug. I think it should process nvme by default and probably with the regex in place it shouldn't do any additional filtering.

Comment 11 Jaroslav Škarvada 2022-02-02 22:40:34 UTC

Upstream PR:
https://github.com/redhat-performance/tuned/pull/395

Comment 21 errata-xmlrpc 2022-05-10 15:31:16 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 (tuned 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:2106