Bug 1330473

Summary: Disabled performance in cockpit doesn't work in node
Product: Red Hat Enterprise Linux 7 Reporter: wanghui <huiwa>
Component: cockpitAssignee: Dominik Perpeet <dperpeet>
Status: CLOSED ERRATA QA Contact: Jan Ščotka <jscotka>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2CC: bugs, cshao, fdeutsch, huzhao, leiwang, stefw, weiwang, yaniwang
Target Milestone: pre-dev-freezeKeywords: Extras
Target Release: 7.3   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: cockpit-0.114-2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-04 13:47:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1329957    

Description wanghui 2016-04-26 10:09:21 UTC
Description of problem:
Disabled performance in cockpit doesn't work in node.

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

How reproducible:

Steps to Reproduce:
1. Anaconda install NGN 4.0.
2. Start cockpit service.
3. Change the performance profile to none from cockpit.
4. Check the performance in node.
#tuned-adm active

Actual results:
1. After step4, the output is as follows and it's the former profile.
# tuned-adm active
Current active profile: latency-performance 

Expected results:
1. It should be disabled.

Additional info:

Comment 5 Stef Walter 2016-07-07 16:24:12 UTC
Included in 0.112. Over do Dominik for tracking the final release into RHEL.

Comment 7 Stef Walter 2016-07-14 12:22:56 UTC
Cockpit integration test here: https://github.com/cockpit-project/cockpit/blob/master/test/verify/check-tuned#L100

Comment 10 errata-xmlrpc 2016-08-04 13:47:11 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, and where to find the updated
files, follow the link below.

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