Bug 1152188

Summary: Irqbalance didn't log failing to set SMP affinity
Product: Red Hat Enterprise Linux 6 Reporter: Andrej Manduch <amanduch>
Component: irqbalanceAssignee: Petr Holasek <pholasek>
Status: CLOSED ERRATA QA Contact: Andrej Manduch <amanduch>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.7CC: dhoward, emcnabb, jeder, pholasek
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: irqbalance-1.0.7-2.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1155799 (view as bug list) Environment:
Last Closed: 2015-07-22 06:11:28 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: 1155799    
Attachments:
Description Flags
output from `strace -e trace=file irqbalance --debug --oneshot` none

Description Andrej Manduch 2014-10-13 14:31:09 UTC
Created attachment 946426 [details]
output from `strace -e trace=file irqbalance --debug --oneshot`

Description of problem:

If irqbalance doesn't have right to change irq smp affinity it will silliently continue without any warning in logs what so ever.

How reproducible:

Run irqbalance with 

Steps to Reproduce:
1. log yourself as regular user
2. set IRQBALANCE_BANNED_CPUS
3. run irqbalancer
4. check /proc/irq/*/smp_affinity if was changed by irqbalance to value coresponding with IRQBALANCE_BANNED_CPUS (if you've done everything right value should stay unchanged due lack of privileges)
5. check irqbalance log (you'll see nothing about failing to set SMP affinity)

Expected results:

I belive I should be able to at least see some warning in logs about failing to set SMP affinity

Additional info:
In attachment I'm sending output from my run of `strace -e trace=file irqbalance --debug --oneshot`

Comment 6 errata-xmlrpc 2015-07-22 06:11:28 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://rhn.redhat.com/errata/RHBA-2015-1279.html