Bug 1392438

Summary: powertop service fails to start
Product: Red Hat Enterprise Linux 7 Reporter: Marko Myllynen <myllynen>
Component: powertopAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED ERRATA QA Contact: Erik Hamera <ehamera>
Severity: unspecified Docs Contact:
Priority: high    
Version: 7.3CC: jskarvad, wdh
Target Milestone: rcKeywords: Patch, Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: powertop-2.3-12.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 21:40:47 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:
Bug Depends On:    
Bug Blocks: 1380362, 1393869    
Attachments:
Description Flags
Updated patch none

Description Marko Myllynen 2016-11-07 14:05:41 UTC 
Description of problem:
Since at least after RHEL 7.3 I'm seeing powertop service failing to start:

# systemctl status powertop.service    
● powertop.service - PowerTOP autotuner
   Loaded: loaded (/usr/lib/systemd/system/powertop.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2016-11-07 15:57:25 EET; 4min 36s ago
  Process: 962 ExecStart=/usr/sbin/powertop --auto-tune (code=exited, status=1/FAILURE)
 Main PID: 962 (code=exited, status=1/FAILURE)

Nov 07 15:57:25 host systemd[1]: Starting PowerTOP autotuner...
Nov 07 15:57:25 host powertop[962]: Loaded 10 prior measurements
Nov 07 15:57:25 host powertop[962]: Error opening terminal: unknown.
Nov 07 15:57:25 host systemd[1]: powertop.service: main process exited, code=exited, status=1/FAILURE
Nov 07 15:57:25 host systemd[1]: Failed to start PowerTOP autotuner.
Nov 07 15:57:25 host systemd[1]: Unit powertop.service entered failed state.
Nov 07 15:57:25 host systemd[1]: powertop.service failed.

Version-Release number of selected component (if applicable):
powertop-2.3-11.el7.x86_64
Comment 1 Jaroslav Škarvada 2016-11-08 09:25:12 UTC 
Thanks for the report, it seems to be an regression. Strange that it hasn't been caught by QE.
Comment 3 Jaroslav Škarvada 2016-11-08 09:51:37 UTC 
Created attachment 1218465 [details]
Updated patch

Updated patch, that caused the regression.
Comment 5 Jaroslav Škarvada 2016-11-08 09:54:57 UTC 
Scratch build for testing:
http://people.redhat.com/jskarvad/rhbz1392438/
Comment 6 Marko Myllynen 2016-11-08 10:12:37 UTC 
(In reply to Jaroslav Škarvada from comment #5)
> Scratch build for testing:
> http://people.redhat.com/jskarvad/rhbz1392438/

Thanks, with this the service starts up again as expected.
Comment 7 W. de Heiden 2017-01-10 14:38:11 UTC 
I was hit by this issue as well. When can the update be expected for RHEL7?
Comment 12 errata-xmlrpc 2017-08-01 21:40:47 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.

https://access.redhat.com/errata/RHBA-2017:2184