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 1234963

Summary:	python-linux-procfs fails to read /proc/PID/flags correctly
Product:	Red Hat Enterprise Linux 7	Reporter:	John Kacur <jkacur>
Component:	tuna	Assignee:	John Kacur <jkacur>
Status:	CLOSED ERRATA	QA Contact:	Jiri Kastner <jkastner>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	acme, bhu, jkastner, williams
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: improper splitting of fields with embedded spaces Consequence: /proc/PID/flags is read incorrectly Fix: Take embedded spaces into account with splitting fields Result: proc/PID/flags is read correctly	Story Points:	---
Clone Of:
Clones:	1255727 (view as bug list)		Environment:
Last Closed:	2015-11-19 12:48:11 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:	1232394, 1255727

Description John Kacur 2015-06-23 15:16:56 UTC

See https://bugzilla.redhat.com/show_bug.cgi?id=1232394
This bugzilla is being opened for the tuna component of the problem in the above bugzilla.

Comment 1 John Kacur 2015-06-25 18:58:15 UTC

Fixed in v0.11.1-10 and up

List of changes since the last are

- dropped the git housekeeping patch, not relevant here
- docs-Remove-stray-a.patch
- CLI-Introduce-nohz_full-N-entity.patch
- tuna-config-Fix-pygtk-import.patch
- tuna-Make-isolate-include-operations-affect-proc-irq.patch
- tuna-Decide-whether-to-isolate-a-thread-based-on-PF_.patch
- tuna-Fix-race-in-is_hardirq_handler.patch
- CLI-Do-not-show-column-headers-when-not-outputting-t.patch
- Correct-a-typo-in-the-net.ipv4.ipfrag_time-help-stri.patch

Although the list is fairly long they fall in the category of either

1. Trivial ones, such as 
 - remove a git house keeping patch
 - spelling fixes in documentation

2. Patches that lead-up to tuna-Fix-race-in-is_hardirq_handler.patch
   which is the patch that fixes the problem here. (along with some patches to python-linux-procfs which will be handled in bugzilla1232394)

Also note that these are all upstream patches. I will be able to drop them in a future update when we rebase the upstrem

Comment 4 errata-xmlrpc 2015-11-19 12:48:11 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-2409.html