Bug 1928618 - NTO may fail to disable stalld when relying on Tuned '[service]' plugin
Summary: NTO may fail to disable stalld when relying on Tuned '[service]' plugin
Keywords:
Status: CLOSED DUPLICATE of bug 1928614
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node Tuning Operator
Version: 4.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Jiří Mencák
QA Contact: Simon
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-15 07:28 UTC by Jiří Mencák
Modified: 2021-02-18 10:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-18 10:27:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.