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 1636959

Summary: pmdaproc only reads the first 1024 bytes of the /proc/*/status file resulting in lost metric values [rhel-7.6.z]
Product: Red Hat Enterprise Linux 7 Reporter: Oneata Mircea Teodor <toneata>
Component: pcpAssignee: Nathan Scott <nathans>
Status: CLOSED ERRATA QA Contact: Michal Kolar <mkolar>
Severity: high Docs Contact: Vladimír Slávik <vslavik>
Priority: urgent    
Version: 7.5CC: brolley, fche, fkrska, kwalker, lberk, mcermak, mgoodwin, mkolar, nathans, patrickm, tbowling, toneata, vslavik
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, the Performance Co-Pilot (PCP) toolkit failed to report certain process details on very large systems in some cases. The code reading the process details files was changed so that it can read data of arbitrary length, instead of only the first 1024 bytes. As a result, the described PCP error can no longer happen.
Story Points: ---
Clone Of: 1600262 Environment:
Last Closed: 2018-10-30 12:22:07 UTC Type: ---
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: 1600262    
Bug Blocks:    

Description Oneata Mircea Teodor 2018-10-08 11:14:40 UTC
This bug has been copied from bug #1600262 and has been proposed to be backported to 7.6 z-stream (EUS).

Comment 2 Nathan Scott 2018-10-10 01:55:51 UTC
A build has been prepared with the fix now, beginning errata prep.

Comment 3 Nathan Scott 2018-10-10 01:57:51 UTC
Whoops, no build yet - confused this BZ with 1636960 - this one (for 7.6) is blocked on missing rhel7.6.x+ flag so the build cannot yet proceed.  Otherwise, its good to go.

Comment 4 Nathan Scott 2018-10-11 09:56:34 UTC
Blocked on dist-git branch creation:
https://projects.engineering.redhat.com/browse/RCM-43341

Comment 6 Michal Kolar 2018-10-19 12:25:59 UTC
Verified against pcp-4.1.0-5.el7_6.x86_64.

Comment 10 Frank Ch. Eigler 2018-10-29 21:43:43 UTC
The PM_ERR_APPVERSION code that the user reported would have come from pmda.c:


        case PROC_PID_STATUS_CPUSALLOWED: /* proc.psinfo.cpusallowed */
        if ((atom->cp = _pm_getfield(entry->status_lines.cpusallowed, 1)) == NULL)
            return PM_ERR_APPVERSION;
        break;

which would happen if fetch_proc_pid_status in proc_pid.c ran out of 1024-byte input before it got to the Cpus_allowed_list: line.  The bug report and original doc text is confirmed by reading the code.

Comment 12 errata-xmlrpc 2018-10-30 12:22:07 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://access.redhat.com/errata/RHBA-2018:3345