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 1245677 - The current regex solution breaks tuna and possible others apps with newer kernels
Summary: The current regex solution breaks tuna and possible others apps with newer ke...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: python-linux-procfs
Version: 7.1
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: 7.3
Assignee: John Kacur
QA Contact: Jiri Kastner
URL:
Whiteboard:
Depends On:
Blocks: 1274397 RT7.3-RHELpkgs 1313485
TreeView+ depends on / blocked
 
Reported: 2015-07-22 14:09 UTC by Flavio Leitner
Modified: 2016-11-04 08:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2016-11-04 08:08:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2532 0 normal SHIPPED_LIVE python-linux-procfs bug fix update 2016-11-03 14:17:30 UTC

Description Flavio Leitner 2015-07-22 14:09:12 UTC
Description of problem:

The /proc/interrupts format changed a bit in the newer kernels adding an extra column.
This is how it used to be:
 43:  0   0   0   0   PCI-MSI-edge  virtio0-input.0
This is how it is now:
 43:  0   0   0   0   PCI-MSI 32769-edge  virtio0-input.0

The extra column breaks the 'users' parser.  As a consequence tuna breaks too.

# tuna --irqs='virtio0*' --cpus=0,1,2,3  -x
[]
tuna: --move requires a list of threads/irqs!
[root@localhost ~]# tuna --irqs='*virtio0*' --cpus=0,1,2,3  -x
[32, 33, 34, 26, 27, 28, 29, 30, 31]

Version-Release number of selected component (if applicable):
tuna-0.11.1-8.el7.noarch
python-linux-procfs-0.4.6-2.el7.noarch
Good kernel: 3.10.0-252.el7.x86_64
Bad kernel: vmlinuz-4.1.0-05824-gb922622

How reproducible:
Always, just reboot a guest using the bad kernel version.

Actual results:
tuna regex for irq users is broken

Expected results:
both kernels are supported and the same regex applies.

Additional info:
The bad kernel might not be supported at this moment, but it is useful for testing and might be the case of more advanced kernels, like kernel-rt. In any case, this needs to be fixed to prevent customers to find it later on when the supported kernel gets updated too.

Comment 2 John Kacur 2016-05-23 14:13:05 UTC
The patch to fix this was included in bz1235826

Comment 6 errata-xmlrpc 2016-11-04 08:08:00 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-2016-2532.html


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