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 1851838

Summary: `pcp atopsar` ignores `-e` option (end time)
Product: Red Hat Enterprise Linux 8 Reporter: Denis Volkov <dvolkov>
Component: pcpAssignee: Nathan Scott <nathans>
Status: CLOSED ERRATA QA Contact: Jan Kurik <jkurik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: ---CC: agerstmayr, jkurik, mgoodwin, nathans, pandrade, patrickm, peter.vreman
Target Milestone: rcKeywords: Bugfix, Triaged
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pcp-5.2.1 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1903574 (view as bug list) Environment:
Last Closed: 2021-05-18 15:19:32 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: 1903574    

Description Denis Volkov 2020-06-29 08:11:47 UTC
Description of problem:
`pcp atopsar` ignores `-e` option that specifies the ending   time for the output

Version-Release number of selected component (if applicable):
Reproduced on pcp-5.0.2-5.el8.x86_64

How reproducible:

pcp atopsar -s -R 60 -r y -b 23:00 -e 23:20

        2020/06/22

-------------------------- analysis date: 2020/06/21 --------------------------

23:00:20  pagescan/s   swapin/s  swapout/s        commitspc  commitlim   _swap_
23:10:10        0.00       0.00       0.00            1082M      5326M
23:20:10        0.00       0.00       0.00            1082M      5326M
23:30:10        0.00       0.00       0.00            1082M      5326M
23:40:10        0.00       0.00       0.00            1082M      5326M
^C (the output does not stop at 23:30, but continues...)

pcp atopsar ignores both options:
          -e  finish showing data after specified time
          --finish TIME end of the time window


Expected results:
pcp atopsar should end the output as specified in `-e` or `--finish` options

Comment 1 Nathan Scott 2020-07-21 03:06:27 UTC
This is resolved upstream and will be in pcp-5.2.0

commit 0b861b081760904632c6854247b254174d6fd551
Author: Nathan Scott <nathans>
Date:   Tue Jul 21 13:05:00 2020 +1000

    pcp-atop: fix logic around the end of an optional time window
    
    Regression test qa/1820 is updated to exercise this.
    
    Resolves Red Hat BZ #1851838.

Comment 8 Paulo Andrade 2020-12-01 18:56:42 UTC
Case #02812127 is for rhel7 and somewhat unrelated. Just that it would
not segfault with the pseudo patch:

-        if (HOST_NMETRICS != result->numpmid)
+        if (result == NULL || HOST_NMETRICS != result->numpmid)

to various.c:setup_globals()

User also tested same data on rhel8, where it also crashes.

A new bug report can be opened for the other issue if you prefer, as it is
not a 100% match, just that the patch for this bugzilla would also prevent
the segfault in the linked support case.

Comment 9 Nathan Scott 2020-12-01 21:48:11 UTC
Hi Paulo,

This fix is scheduled for first release in 8.4.0 - there are already pcp builds in brew containing the fix if that's helpful at this time.
There's no planned el7 update resolving this one at this time, if that's urgently needed a new el7 BZ will be required (with usual zstream justification, as there are no more el7 ystream releases).

cheers.

Comment 11 errata-xmlrpc 2021-05-18 15:19:32 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 (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-2021:1754