Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2012243

Summary: tuna: Add distinction between --spread and --move to error message
Product: Red Hat Enterprise Linux 9 Reporter: John Kacur <jkacur>
Component: tunaAssignee: Leah Leshchinsky <lleshchi>
Status: CLOSED ERRATA QA Contact: Kernel Realtime QE <rt-qe>
Severity: low Docs Contact:
Priority: unspecified    
Version: 9.0CC: bhu, lleshchi, mstowell, qzhao, rt-maint, rt-qe
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tuna-0.16-4.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2012241 Environment:
Last Closed: 2022-05-17 15:55:01 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: 2012241    
Bug Blocks: 2020013    

Description John Kacur 2021-10-08 16:13:42 UTC
+++ This bug was initially created as a clone of Bug #2012241 +++

Description of problem:
    
    Currently, the command `tuna --cpus=CPU-LIST --spread` generates an
    error with the warning "tuna: --move requires a list of threads/irqs!".
    Similarly, when the command `tuna --threads=THREAD-LIST --spread` is
    run, it generates the warning "tuna: --move requires a cpu list!".
    
    This can be confusing to the user, especially with commands that use both
    the "--spread" and "--move" flags. The warning should specify "--spread"
    when that is the source of the error.
    
    Check whether the argument is a move or spread and update the warning
    string accordingly.


How reproducible:
Every time 

Steps to Reproduce:
1. tuna --cpus=0,2,3 --spread
OR
2. tuna --threads="ssh*" --spread

Actual results:
1. tuna --cpus=0,2,3 --spread
tuna: --move requires a list of threads/irqs!

2. ./tuna-cmd.py --threads="ssh*" --spread
tuna: --move requires a cpu list!

Expected results:

1. ./tuna-cmd.py --cpus=0,2,3 --spread
tuna: --spread requires a list of threads/irqs!

2. ./tuna-cmd.py --threads="ssh*" --spread
tuna: --spread requires a cpu list!

Comment 8 errata-xmlrpc 2022-05-17 15:55:01 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 (new packages: tuna), 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-2022:3955