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.
Description of problem:
Version-Release number of selected component (if applicable):
pcp-4.3.0-3.el8.x86_64
How reproducible:
Steps to Reproduce:
1.Run pcp atop
2. pass the v option
3. notice the STDATE and STTIME values
Actual results:
The STDATE shows the epoch date whereas STTIME shows wrong start time of a process
Expected results:
STDATE shuld show the correct start date of the process whereas STTIME should show the correct start time of the process
Additional info:
Nathan++ has provided the upstream PR link - https://github.com/performancecopilot/pcp/pull/860
This is fixed upstream through the following commits...
commit 6ba02f04885a6dfca9e196274ccbf903acc3e83b
Author: Shogo Matsumoto <shogo.matsumoto>
Date: Wed Mar 18 21:08:59 2020 +0900
pcp-atop: fix STDATE/STTIME in -v output
STDATE/STTIME of pcp atop -v was wrong (e.g. STDATE=1970/01/01).
A new metric kernel.all.boottime is added and used to fix the issue.
commit 56c8d93abc43c193894955b3cd76dfcc9dc626c4
Author: Nathan Scott <nathans>
Date: Thu Mar 19 15:38:06 2020 +1100
qa: add test 1347 to exercise kernel.all.boottime and pcp-atop
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 (pcp bug fix and enhancement update), 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-2020:4684