Bug 601234 - tuna: no way to change individual thread attributes of thread group in GUI
tuna: no way to change individual thread attributes of thread group in GUI
Status: CLOSED ERRATA
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: realtime-utilities (Show other bugs)
1.2
All Linux
low Severity low
: 2.3
: 2.3
Assigned To: Arnaldo Carvalho de Melo
David Sommerseth
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-07 10:17 EDT by Clark Williams
Modified: 2016-05-22 19:30 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: Ability to change individual thread policy attributes rather than at the thread-group level Reason: Need to be able to modify individual thread to change priority or affinity. Result (if any): Feature added
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-03-06 13:48:09 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Clark Williams 2010-06-07 10:17:37 EDT
Description of problem:
The tuna GUI will now allow changing individual thread scheduling policy inside a thread group (only allows process group change)

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

How reproducible:
always

Steps to Reproduce:
1. run 'cyclictest -t'
2. start tuna gui
3. expand cyclictest threadgroup
4. right mouse on desired thread to change
5. select 'set process attributes'
  
Actual results:
No pop-up dialog to change thread attributes

Expected results:
dialog
Comment 2 David Sommerseth 2013-02-20 13:14:13 EST
Verified on tuna-0.10.4-3.el6rt.noarch.  Followed the reproducer, which now allowed threads to be modified independently.
Comment 4 errata-xmlrpc 2013-03-06 13:48:09 EST
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.

http://rhn.redhat.com/errata/RHBA-2013-0563.html

Note You need to log in before you can comment on or make changes to this bug.