Bug 1928618

Summary:	NTO may fail to disable stalld when relying on Tuned '[service]' plugin
Product:	OpenShift Container Platform	Reporter:	Jiří Mencák <jmencak>
Component:	Node Tuning Operator	Assignee:	Jiří Mencák <jmencak>
Status:	CLOSED DUPLICATE	QA Contact:	Simon <skordas>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.7	CC:	sejug
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-18 10:27:53 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jiří Mencák 2021-02-15 07:28:50 UTC

This bug was initially created as a copy of Bug #1926903

I am copying this bug because: 



Description of problem:
NTO relies on Tuned [service] plugin to start/restart/disable stalld unit file.  However, if the stalld service is started after a Tuned Pod tried to disable the service, the disablement never happens.

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

How reproducible:
Rare -- race.

Steps to Reproduce:
1. Create a Tuned profile for stalld with something like:
[service]
service.stalld=stop,disable

Actual results:
The stalld service may be running even though it was specificaly disabled.

Expected results:
The stalld service stopped/disabled on the host.

Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1923726

Comment 3 Jiří Mencák 2021-02-18 10:27:53 UTC


*** This bug has been marked as a duplicate of bug 1928614 ***