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 1806824 - [RFE] Add interactive mode (i) in atop for changing the time interval on archives
Summary: [RFE] Add interactive mode (i) in atop for changing the time interval on arch...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pcp
Version: 8.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: Nathan Scott
QA Contact: Jan Kurik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-25 05:48 UTC by Yogesh Babar
Modified: 2021-09-17 12:44 UTC (History)
5 users (show)

Fixed In Version: pcp-5.2.0
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-18 15:19:30 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Yogesh Babar 2020-02-25 05:48:56 UTC
Description of problem:

   The pcp atop does not accept the 'i' (interactive mode to change the time interval) when running against the archive file. It says "Not yet possible when viewing raw file". 

The below works though: 

    #pcp -a <archive_filename> atop <interval>  

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 -r <archive_file_name>
2. press i 
3. 

Actual results:

   you will get an error "Not yet possible when viewing raw file" 

Expected results:

   It should accept the user-defined time interval with 'i'. 

Additional info:

#pcp -a <archive_filename> atop <interval>   

this works perfectly

Comment 2 Nathan Scott 2020-07-22 07:47:10 UTC
This is fixed upstream via the following commit:

commit d3011a416e318697ee1a7c9d406e4766b2ee3cd7
Author: Nathan Scott <nathans>
Date:   Wed Jul 22 17:45:32 2020 +1000

    pcp-atop: implement several RFEs relating to time navigation
    
    Adds interactive mode (i) in atop for changing time interval.
    Adds the branch (b) to certain time feature in atop.
    
    Fixes option 'T' for stepping backward one sample in time and
    also enables 'k' option for localhost contexts.
    
    Resolves Red Hat BZs 1806824, 1847925 and 1806927.

Comment 3 Yogesh Babar 2020-07-27 05:28:42 UTC
Waiting it to be added in our Red Hat shipped packages. Thanks.

Comment 12 errata-xmlrpc 2021-05-18 15:19:30 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


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